Health application user interfaces

ABSTRACT

The present disclosure generally relates to health-related user interfaces. In some embodiments, user interfaces for managing health-related data are described. In some embodiments, user interfaces for viewing health data are described. In some embodiments, user interfaces related to sharing health data are described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.18/078,444, filed on Dec. 9, 2022, entitled “HEALTH APPLICATION USERINTERFACES,” which is a continuation of U.S. patent application Ser. No.17/041,415, now U.S. Pat. No. 11,527,316, filed on Sep. 24, 2020,entitled “HEALTH APPLICATION USER INTERFACES,” which is a U.S. NationalStage patent application of PCT/US20/35164, filed on May 29, 2020,entitled “HEALTH APPLICATION USER INTERFACES,” which is a continuationof U.S. patent application Ser. No. 16/880,714, now U.S. Pat. No.11,152,100, filed on May 21, 2020, entitled “HEALTH APPLICATION USERINTERFACES,” which claims priority to U.S. Provisional PatentApplication Ser. No. 62/856,061, filed on Jun. 1, 2019, entitled “HEALTHAPPLICATION USER INTERFACES,” the contents of each of which are herebyincorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques and user interfaces for managinghealth information and functions.

BACKGROUND

Electronic devices collect, store, and access health-related informationfor users. Such devices provide the user with the ability to managehealth information and corresponding functions using the electronicdevice.

BRIEF SUMMARY

Some techniques for managing health information and functions usingelectronic devices, however, are generally cumbersome and inefficient.For example, some existing techniques use a complex and time-consuminguser interface, which can include multiple key presses or keystrokes.Existing techniques require more time than necessary, wasting user timeand device energy. This latter consideration is particularly importantin battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for managing healthinformation and functions. Such methods and interfaces optionallycomplement or replace other methods for managing health information andfunctions. Such methods and interfaces reduce the cognitive burden on auser and produce a more efficient human-machine interface. Forbattery-operated computing devices, such methods and interfaces conservepower and increase the time between battery charges.

In accordance with some embodiments, a method is described. In someembodiments, the method is performed at an electronic device with adisplay device. In some embodiments, the method comprises: displaying,via the display device, a first instance of a first user interfaceincluding a first notification that, when selected, causes display of afirst set of data; and after displaying the first instance of the firstuser interface, displaying a second instance of the first userinterface, where: in accordance with a determination that a set ofinteraction criteria are met, the set of interaction criteria includinga criterion that is met when the first set of data has been displayed,and in accordance with a determination that a first set of removalcriteria are not met, the first set of removal criteria including afirst criterion that is based on a first period of time, the secondinstance of the first user interface includes the first notification; inaccordance with a determination that the set of interaction criteria aremet and in accordance with a determination that the first set of removalcriteria are met, the second instance of the first user interface doesnot include the first notification; in accordance with a determinationthat the set of interaction criteria are not met and in accordance witha determination that a second set of removal criteria are not met, thesecond set of removal criteria including a second criterion that isbased on a second period of time that is greater than the first periodof time, the second instance of the first user interface includes thefirst notification; and in accordance with a determination that the setof interaction criteria are not met and in accordance with adetermination that the second set of removal criteria are met, thesecond instance of the first user interface does not include the firstnotification.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: displaying, via the display device, a first instanceof a first user interface including a first notification that, whenselected, causes display of a first set of data; and after displayingthe first instance of the first user interface, displaying a secondinstance of the first user interface, where: in accordance with adetermination that a set of interaction criteria are met, the set ofinteraction criteria including a criterion that is met when the firstset of data has been displayed, and in accordance with a determinationthat a first set of removal criteria are not met, the first set ofremoval criteria including a first criterion that is based on a firstperiod of time, the second instance of the first user interface includesthe first notification; in accordance with a determination that the setof interaction criteria are met and in accordance with a determinationthat the first set of removal criteria are met, the second instance ofthe first user interface does not include the first notification; inaccordance with a determination that the set of interaction criteria arenot met and in accordance with a determination that a second set ofremoval criteria are not met, the second set of removal criteriaincluding a second criterion that is based on a second period of timethat is greater than the first period of time, the second instance ofthe first user interface includes the first notification; and inaccordance with a determination that the set of interaction criteria arenot met and in accordance with a determination that the second set ofremoval criteria are met, the second instance of the first userinterface does not include the first notification.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: displaying, via the display device, a first instanceof a first user interface including a first notification that, whenselected, causes display of a first set of data; and after displayingthe first instance of the first user interface, displaying a secondinstance of the first user interface, where: in accordance with adetermination that a set of interaction criteria are met, the set ofinteraction criteria including a criterion that is met when the firstset of data has been displayed, and in accordance with a determinationthat a first set of removal criteria are not met, the first set ofremoval criteria including a first criterion that is based on a firstperiod of time, the second instance of the first user interface includesthe first notification; in accordance with a determination that the setof interaction criteria are met and in accordance with a determinationthat the first set of removal criteria are met, the second instance ofthe first user interface does not include the first notification; inaccordance with a determination that the set of interaction criteria arenot met and in accordance with a determination that a second set ofremoval criteria are not met, the second set of removal criteriaincluding a second criterion that is based on a second period of timethat is greater than the first period of time, the second instance ofthe first user interface includes the first notification; and inaccordance with a determination that the set of interaction criteria arenot met and in accordance with a determination that the second set ofremoval criteria are met, the second instance of the first userinterface does not include the first notification.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: displaying, via the display device,a first instance of a first user interface including a firstnotification that, when selected, causes display of a first set of data;and after displaying the first instance of the first user interface,displaying a second instance of the first user interface, where: inaccordance with a determination that a set of interaction criteria aremet, the set of interaction criteria including a criterion that is metwhen the first set of data has been displayed, and in accordance with adetermination that a first set of removal criteria are not met, thefirst set of removal criteria including a first criterion that is basedon a first period of time, the second instance of the first userinterface includes the first notification; in accordance with adetermination that the set of interaction criteria are met and inaccordance with a determination that the first set of removal criteriaare met, the second instance of the first user interface does notinclude the first notification; in accordance with a determination thatthe set of interaction criteria are not met and in accordance with adetermination that a second set of removal criteria are not met, thesecond set of removal criteria including a second criterion that isbased on a second period of time that is greater than the first periodof time, the second instance of the first user interface includes thefirst notification; and in accordance with a determination that the setof interaction criteria are not met and in accordance with adetermination that the second set of removal criteria are met, thesecond instance of the first user interface does not include the firstnotification.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;means for displaying, via the display device, a first instance of afirst user interface including a first notification that, when selected,causes display of a first set of data; and means, after displaying thefirst instance of the first user interface, for displaying a secondinstance of the first user interface, where: in accordance with adetermination that a set of interaction criteria are met, the set ofinteraction criteria including a criterion that is met when the firstset of data has been displayed, and in accordance with a determinationthat a first set of removal criteria are not met, the first set ofremoval criteria including a first criterion that is based on a firstperiod of time, the second instance of the first user interface includesthe first notification; in accordance with a determination that the setof interaction criteria are met and in accordance with a determinationthat the first set of removal criteria are met, the second instance ofthe first user interface does not include the first notification; inaccordance with a determination that the set of interaction criteria arenot met and in accordance with a determination that a second set ofremoval criteria are not met, the second set of removal criteriaincluding a second criterion that is based on a second period of timethat is greater than the first period of time, the second instance ofthe first user interface includes the first notification; and inaccordance with a determination that the set of interaction criteria arenot met and in accordance with a determination that the second set ofremoval criteria are met, the second instance of the first userinterface does not include the first notification.

In accordance with some embodiments, a method is described. In someembodiments, the method is performed at an electronic device with adisplay device. In some embodiments, the method comprises: receivingfirst health data; receiving a request to display a first userinterface; in response to receiving the request, displaying, via thedisplay device, the first user interface including: a first region: inaccordance with a determination that a type of data corresponding to thefirst health data has been identified by user input, including a firstrepresentation of the first health data; and in accordance with adetermination that the type of data corresponding to the first healthdata has not been identified by user input, not including therepresentation of the first health data; and a second region: inaccordance with a determination that a first set of highlight criteriaare met, including a second representation of the first health datadifferent from the first representation; and in accordance with adetermination that the first set of highlight criteria are not met, notincluding the second representation of the first health data.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: receiving first health data; receiving a request todisplay a first user interface; in response to receiving the request,displaying, via the display device, the first user interface including:a first region: in accordance with a determination that a type of datacorresponding to the first health data has been identified by userinput, including a first representation of the first health data; and inaccordance with a determination that the type of data corresponding tothe first health data has not been identified by user input, notincluding the representation of the first health data; and a secondregion: in accordance with a determination that a first set of highlightcriteria are met, including a second representation of the first healthdata different from the first representation; and in accordance with adetermination that the first set of highlight criteria are not met, notincluding the second representation of the first health data.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: receiving first health data; receiving a request todisplay a first user interface; in response to receiving the request,displaying, via the display device, the first user interface including:a first region: in accordance with a determination that a type of datacorresponding to the first health data has been identified by userinput, including a first representation of the first health data; and inaccordance with a determination that the type of data corresponding tothe first health data has not been identified by user input, notincluding the representation of the first health data; and a secondregion: in accordance with a determination that a first set of highlightcriteria are met, including a second representation of the first healthdata different from the first representation; and in accordance with adetermination that the first set of highlight criteria are not met, notincluding the second representation of the first health data.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving first health data;receiving a request to display a first user interface; in response toreceiving the request, displaying, via the display device, the firstuser interface including: first region: in accordance with adetermination that a type of data corresponding to the first health datahas been identified by user input, including a first representation ofthe first health data; and in accordance with a determination that thetype of data corresponding to the first health data has not beenidentified by user input, not including the representation of the firsthealth data; and a second region: in accordance with a determinationthat a first set of highlight criteria are met, including a secondrepresentation of the first health data different from the firstrepresentation; and in accordance with a determination that the firstset of highlight criteria are not met, not including the secondrepresentation of the first health data.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;means for receiving first health data; means for receiving a request todisplay a first user interface; and means, responsive to receiving therequest, for displaying, via the display device, the first userinterface including: a first region: in accordance with a determinationthat a type of data corresponding to the first health data has beenidentified by user input, including a first representation of the firsthealth data; and in accordance with a determination that the type ofdata corresponding to the first health data has not been identified byuser input, not including the representation of the first health data;and a second region: in accordance with a determination that a first setof highlight criteria are met, including a second representation of thefirst health data different from the first representation; and inaccordance with a determination that the first set of highlight criteriaare not met, not including the second representation of the first healthdata.

In accordance with some embodiments, a method is described. In someembodiments, the method is performed at an electronic device with adisplay device. In some embodiments, the method comprises: receivingclinical health record data corresponding to a particular healthinstitution; receiving a request to display a first user interface; andin response to receiving the request, displaying, via the displaydevice, the first user interface including: a first region correspondingto a first type of clinical health record, where the first regionincludes: in accordance with a determination that a first clinicalhealth record of the first type of clinical health record fails to meeta first set of graphing criteria, a first textual representation for thefirst clinical health record based on the clinical health record data,where the first user interface does not include a graphicalrepresentation for the first clinical health record; and in accordancewith a determination that the first clinical health meets the first setof graphing criteria, a first graphical representation for the firstclinical health record based on the clinical health record data; and asecond region corresponding to a second type of clinical health record,where the second region includes: in accordance with a determinationthat a second clinical health record of the second type of clinicalhealth record fails to meet the first set of graphing criteria, a secondtextual representation for the second clinical health record based onthe clinical health record data, where the user interface does notinclude a graphical representation for the second clinical healthrecord; and in accordance with a determination that the second clinicalhealth record meets the first set of graphing criteria, a secondgraphical representation for the second clinical health record based onthe clinical health record data.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: receiving clinical health record data corresponding toa particular health institution; receiving a request to display a firstuser interface; and in response to receiving the request, displaying,via the display device, the first user interface including: a firstregion corresponding to a first type of clinical health record, wherethe first region includes: in accordance with a determination that afirst clinical health record of the first type of clinical health recordfails to meet a first set of graphing criteria, a first textualrepresentation for the first clinical health record based on theclinical health record data, where the first user interface does notinclude a graphical representation for the first clinical health record;and in accordance with a determination that the first clinical healthmeets the first set of graphing criteria, a first graphicalrepresentation for the first clinical health record based on theclinical health record data; and a second region corresponding to asecond type of clinical health record, where the second region includes:in accordance with a determination that a second clinical health recordof the second type of clinical health record fails to meet the first setof graphing criteria, a second textual representation for the secondclinical health record based on the clinical health record data, wherethe user interface does not include a graphical representation for thesecond clinical health record; and in accordance with a determinationthat the second clinical health record meets the first set of graphingcriteria, a second graphical representation for the second clinicalhealth record based on the clinical health record data.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: receiving clinical health record data corresponding toa particular health institution; receiving a request to display a firstuser interface; and in response to receiving the request, displaying,via the display device, the first user interface including: a firstregion corresponding to a first type of clinical health record, wherethe first region includes: in accordance with a determination that afirst clinical health record of the first type of clinical health recordfails to meet a first set of graphing criteria, a first textualrepresentation for the first clinical health record based on theclinical health record data, where the first user interface does notinclude a graphical representation for the first clinical health record;and in accordance with a determination that the first clinical healthmeets the first set of graphing criteria, a first graphicalrepresentation for the first clinical health record based on theclinical health record data; and a second region corresponding to asecond type of clinical health record, where the second region includes:in accordance with a determination that a second clinical health recordof the second type of clinical health record fails to meet the first setof graphing criteria, a second textual representation for the secondclinical health record based on the clinical health record data, wherethe user interface does not include a graphical representation for thesecond clinical health record; and in accordance with a determinationthat the second clinical health record meets the first set of graphingcriteria, a second graphical representation for the second clinicalhealth record based on the clinical health record data.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving clinical health recorddata corresponding to a particular health institution; receiving arequest to display a first user interface; and in response to receivingthe request, displaying, via the display device, the first userinterface including: a first region corresponding to a first type ofclinical health record, where the first region includes: in accordancewith a determination that a first clinical health record of the firsttype of clinical health record fails to meet a first set of graphingcriteria, a first textual representation for the first clinical healthrecord based on the clinical health record data, where the first userinterface does not include a graphical representation for the firstclinical health record; and in accordance with a determination that thefirst clinical health meets the first set of graphing criteria, a firstgraphical representation for the first clinical health record based onthe clinical health record data; and a second region corresponding to asecond type of clinical health record, where the second region includes:in accordance with a determination that a second clinical health recordof the second type of clinical health record fails to meet the first setof graphing criteria, a second textual representation for the secondclinical health record based on the clinical health record data, wherethe user interface does not include a graphical representation for thesecond clinical health record; and in accordance with a determinationthat the second clinical health record meets the first set of graphingcriteria, a second graphical representation for the second clinicalhealth record based on the clinical health record data.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;means for receiving clinical health record data corresponding to aparticular health institution; means for receiving a request to displaya first user interface; and means, responsive to receiving the request,for displaying, via the display device, the first user interfaceincluding: a first region corresponding to a first type of clinicalhealth record, where the first region includes: in accordance with adetermination that a first clinical health record of the first type ofclinical health record fails to meet a first set of graphing criteria, afirst textual representation for the first clinical health record basedon the clinical health record data, where the first user interface doesnot include a graphical representation for the first clinical healthrecord; and in accordance with a determination that the first clinicalhealth meets the first set of graphing criteria, a first graphicalrepresentation for the first clinical health record based on theclinical health record data; and a second region corresponding to asecond type of clinical health record, where the second region includes:in accordance with a determination that a second clinical health recordof the second type of clinical health record fails to meet the first setof graphing criteria, a second textual representation for the secondclinical health record based on the clinical health record data, wherethe user interface does not include a graphical representation for thesecond clinical health record; and in accordance with a determinationthat the second clinical health record meets the first set of graphingcriteria, a second graphical representation for the second clinicalhealth record based on the clinical health record data.

In accordance with some embodiments, a method is described. In someembodiments, the method is performed at an electronic device with adisplay device. In some embodiments, the method comprises: receivingclinical health record data, including: first clinical health recorddata corresponding to a first type of clinical health record; and secondclinical health record data corresponding to a second type of clinicalhealth record; receiving a request to display a first user interface; inresponse to receiving the request, displaying, via the display device,the first user interface, including: a first representation, based onthe first clinical health record data, for a first clinical healthrecord of the first type of clinical health record; while displaying thefirst user interface, receiving first user input corresponding toselection of the first representation; in response to receiving thefirst user input: displaying, via the display device, a second userinterface, including: a second representation, based on the firstclinical health record data, for the first clinical health record of thefirst type of clinical health record, where the second representation isdifferent from the first representation; and a third representation,based on the first clinical health record data, for a second clinicalhealth record of the first type of clinical health record, where thethird representation is different from the second representation and thesecond clinical health record of the first type is different from thefirst clinical health record of the first type; while displaying thesecond user interface, receiving second user input corresponding toselection of the third representation; and in response to receiving thesecond user input: displaying, via the display device, a third userinterface, including a fourth representation, based on the firstclinical health record data, for the first clinical health record of thefirst type of clinical health record, where the fourth representation isdifferent from the first representation, and where the fourthrepresentation is different from the second representation.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: receiving clinical health record data, including:first clinical health record data corresponding to a first type ofclinical health record; and second clinical health record datacorresponding to a second type of clinical health record; receiving arequest to display a first user interface; in response to receiving therequest, displaying, via the display device, the first user interface,including: a first representation, based on the first clinical healthrecord data, for a first clinical health record of the first type ofclinical health record; while displaying the first user interface,receiving first user input corresponding to selection of the firstrepresentation; in response to receiving the first user input:displaying, via the display device, a second user interface, including:a second representation, based on the first clinical health record data,for the first clinical health record of the first type of clinicalhealth record, where the second representation is different from thefirst representation; and a third representation, based on the firstclinical health record data, for a second clinical health record of thefirst type of clinical health record, where the third representation isdifferent from the second representation and the second clinical healthrecord of the first type is different from the first clinical healthrecord of the first type; while displaying the second user interface,receiving second user input corresponding to selection of the thirdrepresentation; and in response to receiving the second user input:displaying, via the display device, a third user interface, including afourth representation, based on the first clinical health record data,for the first clinical health record of the first type of clinicalhealth record, where the fourth representation is different from thefirst representation, and where the fourth representation is differentfrom the second representation.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a display device isdescribed. In some embodiments, the one or more programs includeinstructions for: receiving clinical health record data, including:first clinical health record data corresponding to a first type ofclinical health record; and second clinical health record datacorresponding to a second type of clinical health record; receiving arequest to display a first user interface; in response to receiving therequest, displaying, via the display device, the first user interface,including: a first representation, based on the first clinical healthrecord data, for a first clinical health record of the first type ofclinical health record; while displaying the first user interface,receiving first user input corresponding to selection of the firstrepresentation; in response to receiving the first user input:displaying, via the display device, a second user interface, including:a second representation, based on the first clinical health record data,for the first clinical health record of the first type of clinicalhealth record, where the second representation is different from thefirst representation; and a third representation, based on the firstclinical health record data, for a second clinical health record of thefirst type of clinical health record, where the third representation isdifferent from the second representation and the second clinical healthrecord of the first type is different from the first clinical healthrecord of the first type; while displaying the second user interface,receiving second user input corresponding to selection of the thirdrepresentation; and in response to receiving the second user input:displaying, via the display device, a third user interface, including afourth representation, based on the first clinical health record data,for the first clinical health record of the first type of clinicalhealth record, where the fourth representation is different from thefirst representation, and where the fourth representation is differentfrom the second representation.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving clinical health recorddata, including: first clinical health record data corresponding to afirst type of clinical health record; and second clinical health recorddata corresponding to a second type of clinical health record; receivinga request to display a first user interface; in response to receivingthe request, displaying, via the display device, the first userinterface, including: a first representation, based on the firstclinical health record data, for a first clinical health record of thefirst type of clinical health record; while displaying the first userinterface, receiving first user input corresponding to selection of thefirst representation; in response to receiving the first user input:displaying, via the display device, a second user interface, including:a second representation, based on the first clinical health record data,for the first clinical health record of the first type of clinicalhealth record, where the second representation is different from thefirst representation; and a third representation, based on the firstclinical health record data, for a second clinical health record of thefirst type of clinical health record, where the third representation isdifferent from the second representation and the second clinical healthrecord of the first type is different from the first clinical healthrecord of the first type; while displaying the second user interface,receiving second user input corresponding to selection of the thirdrepresentation; and in response to receiving the second user input:displaying, via the display device, a third user interface, including afourth representation, based on the first clinical health record data,for the first clinical health record of the first type of clinicalhealth record, where the fourth representation is different from thefirst representation, and where the fourth representation is differentfrom the second representation.

In accordance with some embodiments, an electronic device is described.In some embodiments, the electronic device includes: a display device;means for receiving clinical health record data, including: firstclinical health record data corresponding to a first type of clinicalhealth record; and second clinical health record data corresponding to asecond type of clinical health record; means for receiving a request todisplay a first user interface; means, responsive to receiving therequest, for displaying, via the display device, the first userinterface, including: a first representation, based on the firstclinical health record data, for a first clinical health record of thefirst type of clinical health record; means, while displaying the firstuser interface, for receiving first user input corresponding toselection of the first representation; means, responsive to receivingthe first user input, for: displaying, via the display device, a seconduser interface, including: a second representation, based on the firstclinical health record data, for the first clinical health record of thefirst type of clinical health record, where the second representation isdifferent from the first representation; and a third representation,based on the first clinical health record data, for a second clinicalhealth record of the first type of clinical health record, where thethird representation is different from the second representation and thesecond clinical health record of the first type is different from thefirst clinical health record of the first type; means, while displayingthe second user interface, for receiving second user input correspondingto selection of the third representation; and means, responsive toreceiving the second user input, for: displaying, via the displaydevice, a third user interface, including a fourth representation, basedon the first clinical health record data, for the first clinical healthrecord of the first type of clinical health record, where the fourthrepresentation is different from the first representation, and where thefourth representation is different from the second representation.

In accordance with some embodiments, a method is described. In someembodiments, the method is performed at an electronic device with adisplay device, where the electronic device is associated with a firstuser account. In some embodiments, the method comprises: receiving arequest to display a first user interface; in response to receiving thefirst request, displaying, via the display device, the first userinterface, including: a first portion, including a first categoryaffordance; and a second portion including a first shared affordancecorresponding to a second user account; while displaying the first userinterface: receiving first user input corresponding to selection of thefirst category affordance; and receiving second user input correspondingto selection of the first shared affordance; in response to receivingthe first user input, displaying, via the display device, a second userinterface, including a representation of first health data associatedwith the first user account for the first category; in response toreceiving the second user input, displaying, via the display device, athird user interface, including: a first portion, including: a secondcategory affordance corresponding to health data associated with thesecond user account for the first category; while displaying the thirduser interface, receiving third user input corresponding to selection ofthe second category affordance; and in response to receiving the thirduser input, displaying, via the display device, a fourth user interface,including a representation of health data associated with the seconduser account for the first category.

In some embodiments, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device, associated with a first useraccount, with a display device is described. In some embodiments, theone or more programs include instructions for: receiving a request todisplay a first user interface; in response to receiving the firstrequest, displaying, via the display device, the first user interface,including: a first portion, including a first category affordance; and asecond portion including a first shared affordance corresponding to asecond user account; while displaying the first user interface:receiving first user input corresponding to selection of the firstcategory affordance; and receiving second user input corresponding toselection of the first shared affordance; in response to receiving thefirst user input, displaying, via the display device, a second userinterface, including a representation of first health data associatedwith the first user account for the first category; in response toreceiving the second user input, displaying, via the display device, athird user interface, including: a first portion, including: a secondcategory affordance corresponding to health data associated with thesecond user account for the first category; while displaying the thirduser interface, receiving third user input corresponding to selection ofthe second category affordance; and in response to receiving the thirduser input, displaying, via the display device, a fourth user interface,including a representation of health data associated with the seconduser account for the first category.

In some embodiments, a transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device, associated with a first useraccount, with a display device is described. In some embodiments, theone or more programs include instructions for: receiving a request todisplay a first user interface; in response to receiving the firstrequest, displaying, via the display device, the first user interface,including: a first portion, including a first category affordance; and asecond portion including a first shared affordance corresponding to asecond user account; while displaying the first user interface:receiving first user input corresponding to selection of the firstcategory affordance; and receiving second user input corresponding toselection of the first shared affordance; in response to receiving thefirst user input, displaying, via the display device, a second userinterface, including a representation of first health data associatedwith the first user account for the first category; in response toreceiving the second user input, displaying, via the display device, athird user interface, including: a first portion, including: a secondcategory affordance corresponding to health data associated with thesecond user account for the first category; while displaying the thirduser interface, receiving third user input corresponding to selection ofthe second category affordance; and in response to receiving the thirduser input, displaying, via the display device, a fourth user interface,including a representation of health data associated with the seconduser account for the first category.

In accordance with some embodiments, an electronic device associatedwith a first user account is disclosed. In some embodiments, theelectronic device includes: a display device; one or more processors;and memory storing one or more programs configured to be executed by theone or more processors, the one or more programs including instructionsfor: receiving a request to display a first user interface; in responseto receiving the first request, displaying, via the display device, thefirst user interface, including: a first portion, including a firstcategory affordance; and a second portion including a first sharedaffordance corresponding to a second user account; while displaying thefirst user interface: receiving first user input corresponding toselection of the first category affordance; and receiving second userinput corresponding to selection of the first shared affordance; inresponse to receiving the first user input, displaying, via the displaydevice, a second user interface, including a representation of firsthealth data associated with the first user account for the firstcategory; in response to receiving the second user input, displaying,via the display device, a third user interface, including: a firstportion, including: a second category affordance corresponding to healthdata associated with the second user account for the first category;while displaying the third user interface, receiving third user inputcorresponding to selection of the second category affordance; and inresponse to receiving the third user input, displaying, via the displaydevice, a fourth user interface, including a representation of healthdata associated with the second user account for the first category.

In accordance with some embodiments, an electronic device associatedwith a first user account is disclosed. In some embodiments, theelectronic device includes: a display device; means for receiving arequest to display a first user interface; means, responsive toreceiving the first request, for displaying, via the display device, thefirst user interface, including: a first portion, including a firstcategory affordance; and a second portion including a first sharedaffordance corresponding to a second user account; means, whiledisplaying the first user interface, for: receiving first user inputcorresponding to selection of the first category affordance; andreceiving second user input corresponding to selection of the firstshared affordance; means, responsive to receiving the first user input,for displaying, via the display device, a second user interface,including a representation of first health data associated with thefirst user account for the first category; means, responsive toreceiving the second user input, for displaying, via the display device,a third user interface, including: a first portion, including: a secondcategory affordance corresponding to health data associated with thesecond user account for the first category; means, while displaying thethird user interface, for receiving third user input corresponding toselection of the second category affordance; and means, in response toreceiving the third user input, for displaying, via the display device,a fourth user interface, including a representation of health dataassociated with the second user account for the first category.

In accordance with some embodiments, a method is described. In someembodiments, the method is performed at a first electronic device with adisplay device. In some embodiments, the method comprises: receiving arequest to share health data associated with the first electronicdevice; in response to receiving the request, displaying, via thedisplay device at a first time, a first notification, including a firstaffordance that, when selected, initiates a process for sharing ofhealth data, associated with the first electronic device, with a secondelectronic device; while displaying the notification, receiving a firstuser input corresponding to selection of the first affordance; inresponse to receiving the first user input, initiating a process forsharing of health data, associated with the first electronic device,with the second electronic device; and after receiving the first userinput: sharing health data associated with the first electronic devicewith the second electronic device; and displaying, via the displaydevice at a second time, a second notification corresponding to thesharing of health data, the second notification including a secondaffordance that, when selected, initiates a process to end sharing ofhealth data, associated with the first electronic device, with thesecond electronic device.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a first electronic device with a displaydevice is described. In some embodiments, the one or more programsinclude instructions for: receiving a request to share health dataassociated with the first electronic device; in response to receivingthe request, displaying, via the display device at a first time, a firstnotification, including a first affordance that, when selected,initiates a process for sharing of health data, associated with thefirst electronic device, with a second electronic device; whiledisplaying the notification, receiving a first user input correspondingto selection of the first affordance; in response to receiving the firstuser input, initiating a process for sharing of health data, associatedwith the first electronic device, with the second electronic device; andafter receiving the first user input: sharing health data associatedwith the first electronic device with the second electronic device; anddisplaying, via the display device at a second time, a secondnotification corresponding to the sharing of health data, the secondnotification including a second affordance that, when selected,initiates a process to end sharing of health data, associated with thefirst electronic device, with the second electronic device.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a first electronic device with a displaydevice is described. In some embodiments, the one or more programsinclude instructions for: receiving a request to share health dataassociated with the first electronic device; in response to receivingthe request, displaying, via the display device at a first time, a firstnotification, including a first affordance that, when selected,initiates a process for sharing of health data, associated with thefirst electronic device, with a second electronic device; whiledisplaying the notification, receiving a first user input correspondingto selection of the first affordance; in response to receiving the firstuser input, initiating a process for sharing of health data, associatedwith the first electronic device, with the second electronic device; andafter receiving the first user input: sharing health data associatedwith the first electronic device with the second electronic device; anddisplaying, via the display device at a second time, a secondnotification corresponding to the sharing of health data, the secondnotification including a second affordance that, when selected,initiates a process to end sharing of health data, associated with thefirst electronic device, with the second electronic device.

In accordance with some embodiments, a first electronic device isdescribed. In some embodiments, the first electronic device includes: adisplay device; one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors, theone or more programs including instructions for: receiving a request toshare health data associated with the first electronic device; inresponse to receiving the request, displaying, via the display device ata first time, a first notification, including a first affordance that,when selected, initiates a process for sharing of health data,associated with the first electronic device, with a second electronicdevice; while displaying the notification, receiving a first user inputcorresponding to selection of the first affordance; in response toreceiving the first user input, initiating a process for sharing ofhealth data, associated with the first electronic device, with thesecond electronic device; and after receiving the first user input:sharing health data associated with the first electronic device with thesecond electronic device; and displaying, via the display device at asecond time, a second notification corresponding to the sharing ofhealth data, the second notification including a second affordance that,when selected, initiates a process to end sharing of health data,associated with the first electronic device, with the second electronicdevice.

In accordance with some embodiments, a first electronic device isdescribed. In some embodiments, the first electronic device includes: adisplay device; means for receiving a request to share health dataassociated with the first electronic device; means, responsive toreceiving the request, for displaying, via the display device at a firsttime, a first notification, including a first affordance that, whenselected, initiates a process for sharing of health data, associatedwith the first electronic device, with a second electronic device;means, while displaying the notification, for receiving a first userinput corresponding to selection of the first affordance; means,responsive to receiving the first user input, for initiating a processfor sharing of health data, associated with the first electronic device,with the second electronic device; and means, after receiving the firstuser input, for: sharing health data associated with the firstelectronic device with the second electronic device; and displaying, viathe display device at a second time, a second notification correspondingto the sharing of health data, the second notification including asecond affordance that, when selected, initiates a process to endsharing of health data, associated with the first electronic device,with the second electronic device.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing health information and functions, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces can complement or replaceother methods for managing health information and functions.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6Z illustrate exemplary user interfaces related to viewinghealth data using an electronic device, in accordance with someembodiments.

FIGS. 7A-7B are a flow diagram illustrating a method for managingnotifications using an electronic device, in accordance with someembodiments.

FIGS. 8A-8B are a flow diagram illustrating a method for managingdisplay of health-related information using an electronic device, inaccordance with some embodiments.

FIGS. 9A-9B are a flow diagram illustrating a method for managingdisplay of clinical health record representations using an electronicdevice, in accordance with some embodiments.

FIGS. 10A-10B are a flow diagram illustrating a method for managingdisplay of clinical health record representations using an electronicdevice, in accordance with some embodiments.

FIGS. 11A-11C are a flow diagram illustrating a method for managingdisplay of health-related information for various user accounts using anelectronic device, in accordance with some embodiments.

FIGS. 12AA-12I illustrate exemplary user interfaces related to viewinghealth data using an electronic device, in accordance with someembodiments.

FIGS. 13A-13G illustrate exemplary user interfaces related to sharinghealth data using an electronic device, in accordance with someembodiments.

FIGS. 14A-14B are a flow diagram illustrating methods related to sharinghealth data, in accordance with some embodiments.

FIGS. 15A-15F illustrate exemplary user interfaces related to viewinghealth data using an electronic device, in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing health information and functions. Forexample, it is advantageous to provide timely health-relatednotifications and cease to display unhelpful notifications. For anotherexample, it is advantageous to emphasize certain health-relatedinformation for the user. Such techniques can reduce the cognitiveburden on a user who manage health information and functions, therebyenhancing productivity. Further, such techniques can reduce processorand battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6Z illustrate exemplary user interfaces relatedto viewing health data using an electronic device, in accordance withsome embodiments. FIGS. 7A-7B are a flow diagram illustrating a methodfor managing notifications using an electronic device, in accordancewith some embodiments. FIGS. 8A-8B are a flow diagram illustrating amethod for managing display of health-related information using anelectronic device, in accordance with some embodiments. FIGS. 9A-9B area flow diagram illustrating a method for managing display of clinicalhealth record representations using an electronic device, in accordancewith some embodiments. FIGS. 10A-10B are a flow diagram illustrating amethod for managing display of clinical health record representationsusing an electronic device, in accordance with some embodiments. FIGS.11A-11C are a flow diagram illustrating a method for managing display ofhealth-related information for various user accounts using an electronicdevice, in accordance with some embodiments. The user interfaces inFIGS. 6A-6Z are used to illustrate the processes described below,including the processes in FIGS. 7A-7B, 8A-8B, 9A-9B, 10A-10B, 11A-11C.FIGS. 12AA-12I illustrate exemplary user interfaces related to viewinghealth data using an electronic device, in accordance with someembodiments. FIGS. 13A-13G illustrate exemplary user interfaces relatedto sharing health data using an electronic device, in accordance withsome embodiments. FIGS. 14A-14B are a flow diagram illustrating methodsrelated to sharing health data, in accordance with some embodiments. Theuser interfaces in FIGS. 13A-13G are used to illustrate the processesdescribed below, including the processes in FIGS. 14A-14B. FIGS. 15A-15Fillustrate exemplary user interfaces related to viewing health datausing an electronic device, in accordance with some embodiments.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that canotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2 ) optionally include an up/downbutton for volume control of speaker 111 and/or microphone 113. The oneor more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, theconnector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone module138 for use in location-based dialing; to camera module 143 aspicture/video metadata; and to applications that provide location-basedservices such as weather widgets, local yellow page widgets, andmap/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700-1100(FIGS. 7A-7B, 8A-8B, 9A-9B, 10A-10B, 11A-11C) and 1400 (FIGS. 14A-14B).A computer-readable storage medium can be any medium that can tangiblycontain or store computer-executable instructions for use by or inconnection with the instruction execution system, apparatus, or device.In some examples, the storage medium is a transitory computer-readablestorage medium. In some examples, the storage medium is a non-transitorycomputer-readable storage medium. The non-transitory computer-readablestorage medium can include, but is not limited to, magnetic, optical,and/or semiconductor storages. Examples of such storage include magneticdisks, optical discs based on CD, DVD, or Blu-ray technologies, as wellas persistent solid-state memory such as flash, solid-state drives, andthe like. Personal electronic device 500 is not limited to thecomponents and configuration of FIG. 5B, but can include other oradditional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A. (Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and/Di isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “ITL”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT′D”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT′D”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT′D”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. Then, representations 578A moves upward, 578B moves upward towardrepresentation 578A, and representation 578C is displayed in proximityof application icon 572B, as shown in FIG. 5H. Representations 578A-578Cform an array above icon 572B. In some embodiments, the animationprogresses in accordance with an intensity of contact 562, as shown inFIGS. 5F-5G, where the representations 578A-578C appear and move upwardsas the intensity of contact 562 increases toward the deep pressintensity threshold (e.g., “ITS”). In some embodiments, the intensity,on which the progress of the animation is based, is the characteristicintensity of the contact. The operations described with reference toFIGS. 5E-5H can be performed using an electronic device similar oridentical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6Z illustrate exemplary user interfaces related to viewinghealth data, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 7A-7B, 8A-8B, 9A-9B, 10A-10B, and11A-11C.

FIG. 6A depicts first electronic device 600 (e.g., a phone) displayinglock user interface 604 via touch-sensitive display device 602 at afirst time (e.g., 9:45). In some examples, first electronic device 600includes one or more features of devices 100, 300, or 500.

In some examples, lock user interface 604 relates to a user interfacedisplayed when first electronic device transitions out of an inactivemode. As depicted in FIG. 6A, lock user interface 604 includes multiplenotifications (e.g., notification 604 a and notification 604 b) issued(e.g., caused to be displayed by first electronic device 600) byprocesses executing on first electronic device 600.

In some examples, notification 604 a was issued by an activity processcorresponding to an activity application (as indicated by icon 604 aa).In some examples, user interface elements corresponding to the activityapplication will include icon 604 aa (or some variant of icon 604 aa,such as a smaller or larger version of icon 604 aa). As depicted in FIG.6A, notification 604 a includes (1) a time that notification 604 a wasissued (e.g., time 604 ad, which indicates “NOW,” referring to 9:45) and(2) a description regarding why notification 604 a was issued (e.g., 604ac).

In some examples, notification 604 b was issued by a clinical healthrecord (CHR) process corresponding to a CHR application (as indicated byicon 604 ba). In some examples, user interface elements corresponding tothe CHR application will include icon 604 ba (or some variant of icon604 ba, such as a smaller or larger version of icon 604 ba). As depictedin FIG. 6A, notification 604 b includes (1) a time that notification 604b was issued (e.g., time 604 bd, which indicates “8:00 AM”) and (2) adescription regarding why notification 604 b was issued (e.g., 604 bc).

FIG. 6B depicts second electronic device 606 (e.g., a watch) displayingnotification 610 via touch-sensitive display device 608 at a second time(e.g., 10:24) after the first time. In some examples, second electronicdevice 606 includes one or more features of devices 100, 300, 500, or600.

In some examples, notification 610 was issued (e.g., caused to bedisplayed by second electronic device 606) by a hearing processcorresponding to a hearing application (as indicated by icon 610 a)executing on second electronic device 606. In some examples, userinterface elements corresponding to the hearing application will includeicon 610 a (or some variant of icon 610 a, such as a smaller or largerversion of icon 610 a). As depicted in FIG. 6B, notification 610includes a description regarding why notification 610 was issued (e.g.,610 b).

FIG. 6C depicts first electronic device 600 displaying home userinterface 612 via touch-sensitive display device 602 at a third timeafter the second time. Home user interface 612 includes multiple icons,each icon corresponding to a different application. For example, homeuser interface 612 includes health icon 612 a to initiate a healthapplication and/or display a user interface of the health application.

FIG. 6C depicts first electronic device 600 receiving user input 613corresponding to health icon 612 a. In some examples, user input 613 isreceived via touch-sensitive display device 602 and corresponds toselection of health icon 612 a (e.g., a tap gesture on health icon 612a). In other examples, other forms of an input can be used, such as aclick via a mouse. In some examples, user input 613 causes a differentuser interface to be displayed via touch-sensitive display device 602,such as display of a user interface of the health application, asdepicted in FIG. 6DA.

FIGS. 6DA-6DE depict first electronic device 600 displaying summary userinterface 614 via touch-sensitive display device 602 at a fourth timeafter the third time. In some examples, summary user interface 614 is auser interface of the health application. As depicted in FIGS. 6DA-6DE,summary user interface 614 includes multiple regions that includedifferent affordances, the regions including a notification region(e.g., the notification region including first notification affordance616, second notification affordance 618, and third notificationaffordance 620), a logging region (e.g., the logging region includinglogging affordance 622), a favorites region (e.g., the favorites regionincluding first favorite affordance 626 a, second favorite affordance626 b, third favorite affordance 626 c, fourth favorite affordance 626d, fifth favorite affordance 626 e, sixth favorite affordance 626 f, andshow all health data affordance 628), a highlights region (e.g., thehighlights region including first highlight affordance 630, secondhighlight affordance 632, and show all highlights affordance 634), ahealth records region (e.g., the health records region including firsthealth records affordance 636, second health records affordance 638, andshow all records affordance 640), an education region, a get more fromhealth region, and an apps region.

In some examples, the notification region includes affordances forhealth-related notifications that have been issued/displayed by a deviceassociated with an account logged into the health application. Forexample, the health-related notifications can be from first electronicdevice 600 (e.g., notification 604 a and notification 604 b, as depictedin FIG. 6A) or another electronic device (e.g., second electronic device606) linked (e.g., both logged into a single account or paired, such asis performed with a smart phone and a corresponding smart watch) toeither first electronic device 600 or the account (e.g., notification610, as depicted in FIG. 6B). In such examples, the notification regionis a location to display information associated with health-relatednotifications in one location that can be viewed after thehealth-related notifications are initially displayed.

As discussed above, the notification region includes first notificationaffordance 616, second notification affordance 618, and thirdnotification affordance 620. In some examples, first notificationaffordance 616 corresponds to (e.g., includes information from)notification 610. In some examples, second notification affordance 618corresponds to (e.g., includes information from) notification 604 a. Insome examples, third notification affordance 620 corresponds to (e.g.,includes information from) notification 604 b. As depicted in FIG. 6DA,notification affordances in the notification region are ordered by datethat a corresponding notification was initially issued (e.g., a mostrecent notification is first, a next most recent notification is next,and so on).

In some examples, notification affordances are removed from thenotification region after a particular amount of time has passed. Insome examples, the particular amount of time varies based on an amountof user interaction associated with a respective notification affordanceor the data related to the affordance. For example, a first notificationaffordance is removed quicker than a second notification affordance whenthe first notification affordance (or a notification corresponding tothe first notification affordance) is interacted with by a user and thesecond notification affordance is not interacted with by a user. Foranother example, a first notification affordance is removed quicker thana second notification affordance when the first notification affordance(or a notification corresponding to the first notification affordance)is displayed for a longer amount of time than the second notificationaffordance (or a notification corresponding to the second notificationaffordance). For another example, a first notification affordance isremoved quicker than a second notification affordance when the firstnotification affordance (or a notification corresponding to the firstnotification affordance) is associated with a type of health data thatis viewed (or interacted with) by a user more often than a type ofhealth data that is associated with the second notification affordance(or a notification corresponding to the second notification affordance).For another example, a first notification affordance is removed quickerthan a second notification affordance when the first notificationaffordance (or a notification corresponding to the first notificationaffordance) has more information (e.g., more detailed information) ormore important information (e.g., as defined by the health application)than the second notification affordance (or a notification correspondingto the second notification affordance). For another example, a firstnotification affordance is removed quicker than a second notificationaffordance when the data corresponding to the first notificationaffordance is viewed on another device (e.g., device 608) (e.g., even ifthe first notification affordance is not interacted with on device 600).Such removal criteria is discussed further with respect to FIG. 6F-6H.

First notification affordance 616 includes icon 616 a, indicating that anotification (e.g., notification 610) corresponding to firstnotification affordance 616 was issued by an application (e.g., thehearing application) represented by icon 616 a. First notificationaffordance 616 includes a header that is visually distinct from the restof first notification affordance 616, the header including title 616 b(indicating what first notification affordance 616 relates to) and time616 c (indicating a time that a notification corresponding to firstnotification affordance 616 was initially issued). In one example, theheader is visually distinct from the rest of first notificationaffordance 616 by being a particular pattern or color that correspondsto the hearing application. In some examples, user interface elementsrelated to the hearing application will include an element that is theparticular pattern or color. As depicted in FIG. 6DA, first notificationaffordance 616 includes content 616 d, which (in some examples) is atleast a portion of content included in the notification corresponding tofirst notification affordance 616.

Second notification affordance 618 includes icon 618 a, indicating thata notification (e.g., notification 604 a) corresponding to secondnotification affordance 618 was issued by an application (e.g., theactivity application) represented by icon 618 a. Second notificationaffordance 618 includes a header that is visually distinct from the restof second notification affordance 618 (and visually distinct from theheaders of first notification affordance 616 and third notificationaffordance 620), the header including title 618 b (indicating whatsecond notification affordance 618 relates to) and time 618 c(indicating a time that a notification corresponding to secondnotification affordance 618 was initially issued). In one example, theheader is visually distinct from other elements by being a particularpattern or color that corresponds to the activity application. In someexamples, user interface elements related to the activity applicationwill include an element that is the particular pattern or color. Asdepicted in FIG. 6DA, second notification affordance 618 includescontent 618 d, which (in some examples) is at least a portion of contentincluded in the notification corresponding to second notificationaffordance 618.

Third notification affordance 620 includes icon 620 a, indicating that anotification (e.g., notification 604 b) corresponding to thirdnotification affordance 620 was issued by an application (e.g., the CHRapplication) represented by icon 620 a. Third notification affordance620 includes a header that is visually distinct from the rest of thirdnotification affordance 620 (and visually distinct from the headers offirst notification affordance 616 and second notification affordance618), the header including title 620 b (indicating what thirdnotification affordance 620 relates to) and time 620 c (indicating atime that a notification corresponding to third notification affordance620 was initially issued). In one example, the header is visuallydistinct from other elements by being a particular pattern or color thatcorresponds to the CHR application. In some examples, user interfaceelements related to the CHR application will include an element that isthe particular pattern or color. As depicted in FIG. 6DA, thirdnotification affordance 620 includes icon 620 d and content 620 e, which(in some examples) is at least a portion of content included in thenotification corresponding to third notification affordance 620. In someexamples, icon 620 d corresponds to a clinical institution thatgenerated a notification associated with third notification affordance620. In such examples, icon 620 d is different from icon 620 a.

In some examples, selection of a notification affordance causes a userinterface of the health application to be displayed, the user interfaceassociated with a corresponding application. For example, selection offirst notification affordance 616 causes a user interface of the healthapplication to be displayed, the user interface including informationfrom the hearing application (sometimes referred to as a hearing dataroom, as depicted in FIG. 6E and further discussed below).

In some examples, the logging region includes affordances for loggingdata. For example, logging affordance 622 relates to logging a cycle.Logging affordance 622 includes icon 622 a, representative of a loggingapplication corresponding to logging affordance 622 (e.g., a cycletracking application). Logging affordance 622 also includes content 622b, describing logging affordance 622 and indicating a last time that auser has logged information associated with the logging application.Logging affordance 622 also includes graphic 622 c, indicating whetherlogging criteria are met (e.g.: when logging criteria are not met,graphic 622 c is a plus sign, indicating that a user has not logged aminimum number of times; when logging criteria are met, graphic 622 c isa check mark, indicating that a user has logged a minimum number oftimes). In some examples, logging affordance 622 when selected, causes auser interface to be displayed that allows a user to log a cycle. Inother examples, the act of selecting logging affordance 622 causes acycle to be logged.

In some examples, a color or pattern associated with a portion oflogging affordance 622 (e.g., a font color of the words “CYCLETRACKING”) are a particular color or pattern corresponding to thelogging application. The particular color or pattern, in some examples,is used on at least a portion of user elements displayed in the healthapplication that correspond to the logging application. In someexamples, the particular color or pattern is visually distinct fromcolors/patterns used for other applications (e.g., the activityapplication, the hearing application, the CHR application, or otherlogging applications).

In some examples, the favorites region includes affordances forhealth-related data that a user has indicated as one of their favorites(as depicted in FIG. 6I and discussed below). In some examples, prior tothe user indicating a favorite, the favorites region includes one ormore pre-defined affordances corresponding to health-related data that asystem has determined that the user would favorite (e.g., based on adevice owned by the user, interactions of the user, the like, defaultfavorites, or any combination thereof).

As discussed above, the favorites region includes first favoriteaffordance 626 a, second favorite affordance 626 b, third favoriteaffordance 626 c, fourth favorite affordance 626 d, fifth favoriteaffordance 626 e, sixth favorite affordance 626 f, and show all healthdata affordance 628. First favorite affordance 626 a, second favoriteaffordance 626 b, and third favorite affordance 626 c correspond tohealth data from an activity application, as indicated by, for example,icon 626 aa.

In some examples, at least a portion of each favorite affordance isvisually distinct to represent a corresponding application (e.g., a fontcolor of title 626 ab, in some examples, corresponds to the activityapplication). In some examples, the element that makes each favoriteaffordance visually distinct is consistent across different userinterface elements (e.g., if a color is the element that is visuallydistinct, other user interface elements corresponding to the activityapplication will include the same color (e.g., the header in secondnotification affordance 618, in some examples, is the same color as thefont of “ACTIVITY” in first favorite affordance 626 a).

As depicted in FIG. 6DA, first favorite affordance 626 a includes a timestamp for the last time health data 626 ac (e.g., move, exercise, andstand metrics) was updated.

As depicted in FIG. 6DB, fourth favorite affordance 626 d includes icon626 da, which is a smaller version of icon 622 a depicted in FIG. 6DA.Such correspondence illustrates that different user interface elementsrelated to the same application, in some examples, include the same iconto represent the application. Icon 626 ea and icon 626 fa are furtherexamples of icons corresponding to different applications. In addition,title 626 db, in some examples, is colored similarly to “CYCLE TRACKING”in content 622 b, to further indicate that both relate to the sameapplication.

In some examples, show all health data affordance 628 causes a userinterface to be displayed that includes representations of all healthdata corresponding to the account associated with the healthapplication. An example of such a user interface is depicted in FIGS.12AA-12AB.

In some examples, the highlights region includes graphicalrepresentations of health data over periods of time that are identifiedby the health application. For example, a particular graphicalrepresentation is displayed when it meets highlight criteria and is notdisplayed when it does not meet the highlight criteria. In someexamples, the highlight criteria is based on differences between healthdata in time periods, time a user has spent viewing a particulargraphic, interaction by a user with a particular graphic or element ofinterface 614, or any combination thereof.

FIG. 6DB depicts electronic device displaying first highlight affordance630 in the highlight region of summary user interface 614 viatouch-sensitive display device 602. First highlight affordance 630includes icon 630 a, indicating that first highlight affordance 630primarily relates to a heart rate application (in some examples, firsthighlight affordance 630 secondarily relates to a second application(e.g., a workout application) such that first highlight affordance 630is based on data from the second application). In some examples, aportion of first highlight affordance 630 is visually distinguished toidentify that first highlight affordance 630 primarily relates to theheart rate application (e.g., a font color for title 630 b, in someexamples, is a particular color corresponding to the heart rateapplication). First highlight affordance 630 also includes description630 c to indicate information illustrated by first highlight affordance630 (e.g., such as a range of values reached during a workout).

As depicted in FIG. 6DB, first highlight affordance 630 includes graph630 d with representations for heart rate during a workout. Graph 630 dincludes minimum indication 630 e, indicating a minimum value for heartrate during the workout, and maximum indication 630 f, indicating amaximum value for heart rate during the workout. Such indications aredetermined by comparing heart rates at different times during a timeperiod corresponding to the workout to identify a minimum and maximum.

FIG. 6DC depicts electronic device displaying second highlightaffordance 632 in the highlight region of summary user interface 614 viatouch-sensitive display device 602. Second highlight affordance 632includes icon 630 a, indicating that second highlight affordance 632relates to an environmental audio application. In some examples, aportion of second highlight affordance 632 is visually distinguished toidentify that second highlight affordance 632 relates to theenvironmental audio application (e.g., a font color for title 632 b, insome examples, is a particular color corresponding to the environmentalaudio application). Second highlight affordance 632 also includesdescription 632 c to indicate information illustrated by secondhighlight affordance 632 (e.g., such as how the average environmentalaudio level for today is 4 dB higher than the average for yesterday).

As depicted in FIG. 6DC, second highlight affordance 632 includes agraph with an average representation for today (e.g., 632 d) and anaverage representation for yesterday (e.g., 632 e). As depicted in FIG.6DC, each of the an average representation for today and the averagerepresentation for yesterday includes a graphical representation of theaverage and a textual representation of the average. In some examples,the graph represents an amount of a single health data metric comparedbetween time periods of the same length.

As discussed above, the highlights region also includes show allhighlights affordance 634. In some examples, selection of show allhighlights affordance 634 causes a user interface corresponding to thehealth application to be displayed, such as show all highlights userinterface as depicted in FIGS. 6MA-6MD.

In some examples, the health records region includes affordances (e.g.,first health records affordance 636 and second health records affordance638) corresponding to each clinical institution that has sent healthrecord data regarding the account associated with the healthapplication. For example, first health records affordance 636 indicatesthat it corresponds to XYZ Medical Center in Palo Alto, CA (see 636 d).For another example, second health records affordance 638 indicates thatit corresponds to ABC Urgent Care in San Jose, CA (see 638 d).

In some examples, each affordance in the health records region includesa title indicating that the affordance corresponds to health records(e.g., title 636 a and title 638 a). As depicted in FIG. 6DC, eachaffordance in the health records region also includes an indication ofwhen a most recent health record from the corresponding clinicalinstitution was received (e.g., first health records affordance 636includes time indication 636 b of 8:00 AM and second health recordsaffordance 638 includes time indication 638 b of 6:00 AM). In someexamples, the affordances in the health records region are ordered basedon when a most recent health record from the corresponding clinicalinstitution was received (e.g., first health records affordance 636 isabove second health records affordance 638 based on a most recent healthrecord corresponding to first health records affordance 636 beingreceived after a most recent health record corresponding to secondhealth records affordance 638). In other examples, the affordances inthe health records region are ordered based on when health recordsupdates were initially issued/generated for the account (e.g., firsthealth records affordance 636 is above second health records affordance638 based on a first health record corresponding to first health recordsaffordance 636 being generated before a second health recordcorresponding to second health records affordance 638). In otherexamples, the affordances in the health records region are ordered basedon a user-defined ordering, such as designating primary and secondaryinstitutions (e.g., where primary institutions are above secondaryinstitutions). In some examples, only primary institutions arerepresented in the health records region, where secondary institutionscan be navigated to using show all health records affordance 640. Insome examples, selection of show all health records affordance 640causes a user interface of the health application to be displayed, theuser interface including all health records received for the accountassociated with the health application (as depicted in FIGS. 60A-60B).

In some examples, each affordance in the health records region includesan indication of which records have been received from the correspondinginstitution. For example, first health records affordance 636 includesindication 636 e, which indicates that health records corresponding tomedications, lab results, and other records have been received from XYZMedical Center. In some examples, indication 636 e is ordered based onwhen health records were received (e.g., medications is before labresults because a health record with health data corresponding tomedications was received more recent than a health record with healthdata corresponding to lab results was received). For another example,second health records affordance 638 includes indication 638 e, whichindicates that health records corresponding to medications have beenreceived from ABC Urgent Care.

In some examples, the education region includes affordances that, whenselected, cause a user interface to be displayed with educationalcontent. In some examples, the get more from health region includesaffordances that, when selected, cause a user interface to be displayedto configure the health application. In some examples, the apps regionincludes affordances corresponding to different applications that aredetermined to relate to the account of the health application.

As depicted in FIG. 6DD, summary user interface 614 includes a pair ofaffordances (e.g., summary affordance 642 a and search affordance 642 b)at the bottom of summary user interface 614 to indicate which section ofthe health application that a current user interface relates (e.g., thevisually distinct affordance (e.g., bolded) indicates which section). Insome examples, selection of a section of the health application that acurrent user interface does not relate (e.g., search affordance 642 b inFIG. 6DD) causes a user interface corresponding to the selected sectionto be displayed (e.g., if search affordance 642 b is selected, a userinterface corresponding to the search section is displayed, as depictedin FIG. 6TA-6 TB). In some examples, selection of an affordancecorresponding to a section that relates to the current user interfacecauses a home interface of the selected section to be displayed (e.g.,summary user interface 614 as depicted in FIG. 6DA for the summarysection and search user interface 684 as depicted in FIGS. 6TA-6TB).

FIG. 6DA depicts first electronic device 600 receiving user input 615corresponding to first notification affordance 616. In some examples,user input 615 is received via touch-sensitive display device 602 andcorresponds to a selection gesture (e.g., tap) on first notificationaffordance 616. In other examples, other forms of selection can be used,such as a click using a mouse. In some examples, user input 615 causes adifferent user interface to be displayed via touch-sensitive displaydevice 602, such as display of environmental audio data room userinterface 644 of the health application as depicted in FIG. 6E.

FIG. 6E depicts first electronic device 600 displaying environmentalaudio data room user interface 644 via touch-sensitive display device602 at a fifth time after the fourth time. In some examples,environmental audio data room user interface 644 is a user interface ofthe health application with information from the environmental audioapplication. As depicted in FIG. 6E, environmental audio data room userinterface 644 includes a graph with data indicating noise levelsdetected by a device throughout a week. In some examples, the data isstored in a location associated with the environmental audio applicationand can be viewed within a user interface of the environmental audioapplication.

Environmental audio data room user interface 644 further includes timescale affordances at the top indicating different time scales (e.g., “D”indicating a day, “W” indicating a week, “M” indicating a month, and “Y”indicating a year). As depicted FIG. 6E, the time scale affordanceindicating week is selected, causing the graph to indicate noise levelsdetected throughout a week. In some examples, selection of a differenttime scale affordance causes the graph to change to indicate noiselevels detected throughout a selected time scale.

As depicted in FIG. 6E, environmental audio data room user interface 644includes a number of affordances at the bottom textually indicatinginformation depicted by the graph. For example, there is a firstaffordance indicating the average throughout the week, a secondaffordance indicating a daily average throughout the week, a thirdaffordance indicating a range throughout the week, and a number of noisenotifications that were issued by the environmental audio applicationthroughout the week. In some examples, selection of one of theaffordances causes the graph to be modified to highlight data in thegraph that corresponds to the selected affordance. For example,selection of the average affordance can cause a line to be inserted inthe graph that indicates the average. For another example, selection ofthe daily average affordance can cause points to be inserted in each barfor each day in the graph to indicate the average for the respectiveday. For another example, selection of the range affordance can cause aportion of the graph to be highlighted where the minimum and maximum ofthe range occurred throughout the week. For another example, selectionof the noise notification affordance can cause a portion of the graph tobe highlighted that caused the noise notifications to be issued.

FIG. 6F depicts first electronic device 600 displaying summary userinterface 614 via touch-sensitive display device 602 at a sixth timeafter the fifth time. In some examples, summary user interface 614 isdisplayed in response to user input corresponding to selection of theback button at the top left of environmental audio data room userinterface 644 (which is depicted in FIG. 6E without the user input).

Summary user interface 614 as depicted in FIG. 6F is scrolled downrelative to summary user interface 614 as depicted in FIG. 6DA (e.g.,the text “SUMMARY” at the top left and the icon of the account at thetop right are no longer displayed). FIG. 6F depicts that firstnotification affordance 616 is still displayed in summary user interface614 after first notification affordance 616 was interacted with (e.g.,selected, as depicted in FIG. 6DA). FIG. 6F also depicts that secondnotification affordance 618 and third notification affordance 620 arealso still displayed in summary user interface 614.

FIG. 6G depicts first electronic device 600 displaying summary userinterface 614 via touch-sensitive display device 602 at a seventh timeafter the sixth time. In some examples, summary user interface 614 isdisplayed in response to user input corresponding to re-display ofsummary user interface 614.

FIG. 6G depicts that first notification affordance 616 is no longerdisplayed in summary user interface 614, even though second notificationaffordance 618 and third notification affordance 620 were receivedbefore first notification affordance 616. Such illustrates thatnotification affordances that are interacted with are, in some examples,removed in a shorter time than notification affordances that are notinteracted with. FIG. 6G depicts that second notification affordance 618and third notification affordance 620 are still displayed in summaryuser interface 614.

FIG. 6H depicts first electronic device 600 displaying summary userinterface 614 via touch-sensitive display device 602 at an eighth timeafter the seventh time. In some examples, summary user interface 614 isre-displayed relative to touch-sensitive display device 602 at theseventh time (as depicted in FIG. 6G).

FIG. 6H depicts that third notification affordance 620 is no longerdisplayed in summary user interface 614, due at least partially to (1) anotification corresponding to third notification affordance 620 beingissued before a notification corresponding to second notificationaffordance 618 and (2) neither the notification corresponding to thirdnotification affordance 620, third notification affordance 620, thenotification corresponding to second notification affordance 618, norsecond notification affordance 618 has been interacted with by a user.Such illustrates that notification affordances that have not beeninteracted with are removed based on chronological order when issued(e.g., older notification affordances are removed first). FIG. 6Hdepicts that second notification affordance 618 is still displayed insummary user interface 614.

FIG. 6H depicts first electronic device 600 receiving user input 625corresponding to edit affordance 624. In some examples, user input 625is received via touch-sensitive display device 602 and corresponds to aselection gesture (e.g., tap) on edit affordance 624. In other examples,other forms of selection can be used, such as a click using a mouse. Insome examples, user input 625 causes a different user interface to bedisplayed via touch-sensitive display device 602, such as display ofedit user interface 646 as depicted in FIG. 6I.

FIG. 6I depicts first electronic device 600 displaying edit userinterface 646 via touch-sensitive display device 602 at a ninth timeafter the eighth time. In some examples, edit user interface 646 is auser interface of the health application allowing a user to add and/orremove favorites to be displayed in the favorites region of summary userinterface 614.

As depicted in FIG. 6I, edit user interface 646 includes existing dataaffordance 646 a and all affordance 646 b for switching between views ofedit user interface 646. For example, user input corresponding toselection of existing data affordance 646 a causes edit user interface646 to display an existing data view, as depicted in FIG. 6I anddiscussed below. Similarly, user input corresponding to selection of allaffordance 646 b causes edit user interface 646 to display an all dataview (not illustrated), which includes all possible health data typesfor adding and/or removing from the favorites region.

In the view corresponding to existing data affordance 646 a (as depictedin FIG. 6I), edit user interface 646 includes representations for healthdata types that the account has at least some health data for (e.g., arepresentation of a health data type is displayed when the healthapplication has access to health data of the health data type for theaccount (e.g., there has been at least some health data of the healthdata type stored for the account)). In such examples, edit userinterface 646 in the view corresponding to existing data affordance 646a does not include any representations for health data types for whichthe account has no health data for (e.g., a representation for a healthdata type is not displayed when the health application does not haveaccess to health data of the health data type for the account (e.g.,there is no health data of the health data type stored for theaccount)).

In either view, selection of a representation of a health data typecauses a favorite affordance for the health data type to be added to thefavorites region of summary user interface 614, allowing a user to viewstored data for the health data type from summary user interface 614. Asdepicted in FIG. 6I, a representation of a health data type is indicatedas being selected by including an indication that is visually distinctfrom other indications within the representation. For example,representation 646 c includes an indication indicating that a favoriteaffordance for the health data type corresponding to representation 646c is to be displayed in the favorites region of summary user interface614. For another example, representation 646 d includes an indicationindicating that a favorite affordance for the health data typecorresponding to representation 646 c is not to be displayed in thefavorites region of summary user interface 614. As depicted in FIG. 6I,groups of representations for health data types are displayed via edituser interface 646. For example, edit user interface 646 includes agroup of representations corresponding to activity, body measurements,and heart, where each representation within a group of representationsis related.

FIG. 6J depicts first electronic device 600 displaying summary userinterface 614 via touch-sensitive display device 602 at a tenth timeafter the ninth time. In some examples, summary user interface 614 isdisplayed in response to user input corresponding to selection of thedone button at the top right of edit user interface 646 (which isdepicted in FIG. 6I without the user input). Summary user interface 614as depicted in FIG. 6J is scrolled down relative to summary userinterface 614 as depicted in FIG. 6H (e.g., logging affordance 622 is nolonger displayed in FIG. 6J).

FIG. 6J depicts first electronic device 600 receiving user input 627corresponding to second favorite affordance 626 b. In some examples,user input 627 is received via touch-sensitive display device 602 andcorresponds to a selection gesture (e.g., tap) on second favoriteaffordance 626 b. In other examples, other forms of selection can beused, such as a click using a mouse. In some examples, user input 627causes a different user interface to be displayed via touch-sensitivedisplay device 602, such as display of steps data room user interface648 as depicted in FIGS. 6KA-6KB.

FIGS. 6KA-6KB depict first electronic device 600 displaying steps dataroom user interface 648 via touch-sensitive display device 602 at aneleventh time after the tenth time. In some examples, steps data roomuser interface 648 is displayed in response to user input correspondingto selection of second favorite affordance 626 b in summary userinterface 614, as depicted in FIG. 6J.

In some examples, steps data room user interface 648 is a user interfaceof the health application with information from the activityapplication. As depicted in FIG. 6KA, steps data room user interface 648includes graph 648 a with representations of health data associated withsteps throughout a day. In some examples, the health data is stored in alocation associated with the activity application and can be viewedwithin a user interface of the activity application.

Steps data room user interface 648 further includes time scaleaffordances at the top indicating different time scales (e.g., “D”indicating a day, “W” indicating a week, “M” indicating a month, and “Y”indicating a year). As depicted FIG. 6KA, the time scale affordanceindicating day is selected, causing the graph to indicate number ofsteps detected throughout a day. In some examples, selection of adifferent time scale affordance causes the graph to change to indicatenumber of steps detected throughout a selected time scale.

Steps data room user interface 648 includes a highlight sectionincluding highlights associated with steps. As depicted in FIG. 6KA,steps data room user interface 648 includes a single highlight (e.g.,648 b) depicting how the number of steps increased over a time period.It should be recognized that other highlights might be included in thehighlight section. In some examples, identifying which highlights todisplay in steps data room user interface 648 includes a similardetermination as discussed above for the highlights region. Steps dataroom user interface 648 further includes description 648 c regardingwhat it means to be a step and add affordance 468 to cause steps to beadded to the favorites region in summary user interface 614.

Referring to FIG. 6KB, steps data room user interface 648 includes (1)steps apps section 648 e with links to suggested apps related to steps(e.g., a link to an app store or a link to an application installed onfirst electronic device 600), (2) options section 648 f with variousoptions related to steps, and (3) education section 648 g withaffordances, which, when selected, cause a user interface to bedisplayed with content pertaining to steps.

FIG. 6L depicts first electronic device 600 displaying summary userinterface 614 via touch-sensitive display device 602 at a twelfth timeafter the eleventh time. In some examples, summary user interface 614 isdisplayed in response to user input corresponding to selection of theback to summary affordance at the top left of steps data room userinterface 648 (which is depicted in FIG. 6KA without the user input).Summary user interface 614 as depicted in FIG. 6L is scrolled downrelative to summary user interface 614 as depicted in FIG. 6J (e.g., thefavorites region is no longer displayed and the highlights region isdisplayed in FIG. 6L).

FIG. 6L depicts first electronic device 600 receiving user input 635corresponding to show all highlights affordance 634. In some examples,user input 635 is received via touch-sensitive display device 602 andcorresponds to a selection gesture (e.g., tap) on show all highlightsaffordance 634. In other examples, other forms of selection can be used,such as a click using a mouse. In some examples, user input 635 causes adifferent user interface to be displayed via touch-sensitive displaydevice 602, such as display of all highlights user interface 650 asdepicted in FIGS. 6MA-6MD.

FIGS. 6MA-6MD depict first electronic device 600 displaying allhighlights user interface 650 via touch-sensitive display device 602 ata thirteenth time after the twelfth time. In some examples, allhighlights user interface 650 is displayed in response to user inputcorresponding to selection of show all highlights affordance 634 insummary user interface 614, as depicted in FIG. 6L.

In some examples, all highlights user interface 650 is a user interfaceof the health application with a list of highlights currently identified(e.g., identifying is based on the determination discussed aboveregarding the highlights region, such that not all highlights generatedare included in all highlights user interface 650 (e.g., only highlightsmeeting a display criteria are displayed in all highlights userinterface 650) by the health application for the account. FIG. 6MAdepicts first electronic device 600 displaying first highlightaffordance 630 and second highlight affordance 632, which were alsodisplayed in the highlights region of summary user interface 614 anddiscussed above.

FIG. 6MB depicts first electronic device 600 displaying third highlightaffordance 652 via touch-sensitive display device 602. Third highlightaffordance 652 includes icon 652 a, indicating that third highlightaffordance 652 relates to a sleep application. In some examples, aportion of third highlight affordance 652 is visually distinguished toidentify that third highlight affordance 652 relates to the sleepapplication (e.g., a font color for title 652 b, in some examples, is aparticular color corresponding to the sleep application). Secondhighlight affordance 632 also includes description 652 c to indicateinformation illustrated by third highlight affordance 652 (e.g., such ashow a user slept an average of 7 hours and 55 minutes this week).

As depicted in FIG. 6MB, third highlight affordance 652 includes a graphwith representations of how much a user slept each day of the week. Thegraph also includes average line 652 e to visually indicate an averageover the week. In some examples, the graph represents an average over atime period (e.g., a week) that is broken into sub time periods (e.g.,days).

FIG. 6MB depicts first electronic device 600 displaying fourth highlightaffordance 654 via touch-sensitive display device 602. Fourth highlightaffordance 654 includes icon 654 a, indicating that fourth highlightaffordance 654 primarily relates to a water application (in someexamples, fourth highlight affordance 654 secondarily relates to acalendar application). In some examples, a portion of fourth highlightaffordance 654 is visually distinguished to identify that fourthhighlight affordance 654 relates to the water application (e.g., a fontcolor for title 654 b, in some examples, is a particular colorcorresponding to the water application). Fourth highlight affordance 654also includes description 652 c to indicate information illustrated byfourth highlight affordance 654 (e.g., such as how a user logged water21 days in the last 4 weeks).

As depicted in FIG. 6MB, fourth highlight affordance 654 includescalendar 654 d with representations for each day having an indicationwhether a user logged water for a respective day. As depicted in FIG.6MB, representation 654 f is visually distinguished from some otherrepresentations (e.g., representation 654 e, indicating that a userlogged water on a day corresponding to representation 654 f and did notlog water on a day corresponding to representation 654 e). In someexamples, calendar 654 d represents frequency of a single health datametric compared between time periods of the same length.

FIG. 6MC depicts first electronic device 600 displaying fifth highlightaffordance 656 via touch-sensitive display device 602. Fifth highlightaffordance 656 includes icon 656 a, indicating that fifth highlightaffordance 656 primarily relates to a navigation application (in someexamples, fifth highlight affordance 656 secondarily relates to aworkout application). In some examples, a portion of fifth highlightaffordance 656 is visually distinguished to identify that fifthhighlight affordance 656 primarily relates to the navigation application(e.g., a font color for title 656 b, in some examples, is a particularcolor corresponding to the navigation application). Fifth highlightaffordance 656 also includes description 656 c to indicate informationillustrated by fifth highlight affordance 656 (e.g., such as that a userlogged a run of 3.1 miles at an average pace of 8:51).

As depicted in FIG. 6MC, fifth highlight affordance 656 includes map 656d with an indication in map 656 d of a route of the run. Fifth highlightaffordance 656 also includes textual information regarding the run,including distance measurement 656 e (which is in addition to and largerthan the distance included in description 656 c), duration 656 f, andcalories 656 g.

FIG. 6MC depicts first electronic device 600 displaying sixth highlightaffordance 658 via touch-sensitive display device 602. Sixth highlightaffordance 658 includes icon 658 a, indicating that sixth highlightaffordance 658 relates to a workout application. In some examples, aportion of sixth highlight affordance 658 is visually distinguished toidentify that sixth highlight affordance 658 relates to the workoutapplication (e.g., a font color for title 658 b, in some examples, is aparticular color corresponding to the workout application). Sixthhighlight affordance 658 also includes description 658 c to indicateinformation illustrated by sixth highlight affordance 658 (e.g., such asthat a user burned a total of 6500 calories today).

As depicted in FIG. 6MC, sixth highlight affordance 658 includes 4different representations of different workouts recorded in a day. Eachworkout includes an icon corresponding to the type of workout,identification information (e.g., a name) of the type of workout, alength of time of the respective workout, and a number of caloriesburned during the respective workout. In some examples, sixth highlightaffordance 658 represents multiple workouts for a single day in a singlehighlight with heath data for the single day.

FIG. 6MD depicts first electronic device 600 displaying seventhhighlight affordance 660 via touch-sensitive display device 602. Seventhhighlight affordance 660 includes icon 660 a, indicating that seventhhighlight affordance 660 primarily relates to a vitals application. Insome examples, a portion of seventh highlight affordance 660 is visuallydistinguished to identify that seventh highlight affordance 660 relatesto the vitals application (e.g., a font color for title 660 b, in someexamples, is a particular color corresponding to the vitalsapplication). It should be noted that seventh highlight affordance 660does not include a description to indicate information illustrated byseventh highlight affordance 660, showing that not all highlights havesuch a description. As depicted in FIG. 6MD, seventh highlightaffordance 660 includes graph 660 c depicting a beats per minute for auser over time, illustrating how the beats per minute reduced from ahigh point to a lower point.

FIG. 6MD depicts first electronic device 600 displaying eighth highlightaffordance 662 via touch-sensitive display device 602. Eighth highlightaffordance 662 includes icon 662 a, indicating that eighth highlightaffordance 662 relates to an activity application. In some examples, aportion of eighth highlight affordance 662 is visually distinguished toidentify that eighth highlight affordance 662 relates to the activityapplication (e.g., a font color for title 662 b, in some examples, is aparticular color corresponding to the activity application). Eighthhighlight affordance 662 also includes description 662 c to indicateinformation illustrated by eighth highlight affordance 662 (e.g., suchas that a user has taken more steps today than they normally do at thistime of day).

As depicted in FIG. 6MD, eighth highlight affordance 662 includes graph662 d comparing an activity metric for a day (e.g., a current day) overa previous average. For example, graph 662 d includes today line 662 hand a previous average line (comprising first portion 662 g and secondportion 662 i). Today line 662 h depicts a number of steps for a user astime has progressed during a day up until the current time. The previousaverage line depicts a number of steps for a user as time has progressedon average during a number of days prior to the current day. Firstportion 662 g represents time up until the current time and secondportion 662 i represents time after the current time. Graph 662 d alsoincludes a textual indication regarding a number of steps for today anda number of steps as of this time on average over the number of daysprior to the current day. In some examples, sixth highlight affordance658 represents average over a time period compared to today withinstantaneous update of information.

FIG. 6N depicts first electronic device 600 displaying summary userinterface 614 via touch-sensitive display device 602 at a fourteenthtime after the thirteenth time. In some examples, summary user interface614 is displayed in response to user input corresponding to selection ofsummary affordance 642 a in all highlights user interface 650 (which isdepicted in FIG. 6MD without the user input). Summary user interface 614as depicted in FIG. 6N is scrolled down relative to summary userinterface 614 as depicted in FIG. 6L (e.g., the highlights region is nolonger displayed and the health records region is displayed in FIG. 6N).

FIG. 6N depicts first electronic device 600 receiving user input 641corresponding to show all health records affordance 640. In someexamples, user input 641 is received via touch-sensitive display device602 and corresponds to a selection gesture (e.g., tap) on show allhealth records affordance 640. In other examples, other forms ofselection can be used, such as a click using a mouse. In some examples,user input 641 causes a different user interface to be displayed viatouch-sensitive display device 602, such as display of all health datauser interface 664 as depicted in FIGS. 60A-60B.

FIGS. 60A-60B depict first electronic device 600 displaying all healthdata user interface 664 via touch-sensitive display device 602 at afifteenth time after the fourteenth time. In some examples, all healthdata user interface 664 is displayed in response to user inputcorresponding to selection of show all health records affordance 640 insummary user interface 614, as depicted in FIG. 6N.

In some examples, all health data user interface 664 is a user interfaceof the health application with a list of health data received for theaccount. As depicted in FIG. 60A, all health data user interface 664includes all data affordance 664 a and health records affordance 664 bfor switching between views of all health data user interface 664. Forexample, user input corresponding to selection of all data affordance664 a causes all health data user interface 664 to display an all dataview, as depicted in FIG. 12AA. Similarly, user input corresponding toselection of health records affordance 664 b causes all health data userinterface 664 to display a health record view (as depicted in FIGS.60A-60B), which includes all health records received for the account. Insome examples, in response to selection of show all health recordsaffordance 640, the health record view is displayed instead of the alldata view. In such examples, in response to selection of an all healthdata affordance (e.g., all health data affordance 628, as depicted inFIG. 6DB), the all data view is displayed instead of the health recordview.

In the health record view, all health data user interface 664, in someexamples, includes representations for health record types (e.g.,representation 666 is for allergies, representation 666 b is forclinical vitals, representation 666 c is for conditions, representation666 d is for immunizations, representation 666 e is for lab results,representation 666 f is for medications, and representation 666 g is forprocedures). In such examples, the representations for health recordtypes are ordered alphabetically (e.g., allergies before clinical vitalsbefore conditions before immunizations before lab results beforemedications before procedures).

In some examples, each representation in the health record view includesan icon corresponding to the health record type (e.g., icon 666 aacorresponds to allergies, icon 666 ba corresponds to clinical vitals,icon 666 ca corresponds to conditions, icon 666 da corresponds toimmunizations, icon 666 ea corresponds to lab results, icon 666 facorresponds to medications, icon 666 ga corresponds to procedures). Insome examples, a user interface of the health application that includesa user interface element corresponding to the health record type willinclude a version of the corresponding icon.

In some examples, each representation in the health record view includesa list of information corresponding to the respective health recordtype. For example, representation 666 a, which corresponds to allergies,includes a list of items for which health records have indicated that auser associated with the account is allergic to (e.g., pollen, mold,avocado, and shellfish). In some examples, the list of information isordered based on recency (e.g., items that have been more recentlyidentified for a health record type are ordered in front of (e.g.,above) items that have less recently been identified for the healthrecord type). In some examples, all health data user interface 664 inthe health record view will include a representation for a health recordtype even when there is no health records for the health record type.

As depicted in FIG. 60B, all health data user interface 664 includesexternal affordance 666 h. Selection of external affordance 666 h causesa user interface of the health application to be displayed, the userinterface including information from one or more external sources (e.g.,sources external to first electronic device 600). As depicted in FIG.60B, all health data user interface 664 includes unreadable dataaffordance 666 i. Selection of unreadable data affordance 666 i causes auser interface of the health application to be displayed, the userinterface including representations of health records that could not beparsed by a process associated with the health application.

FIG. 60A depicts first electronic device 600 receiving user input 667corresponding to representation 666 e. In some examples, user input 667is received via touch-sensitive display device 602 and corresponds to aselection gesture (e.g., tap) on representation 666 e. In otherexamples, other forms of selection can be used, such as a click using amouse. In some examples, user input 667 causes a different userinterface to be displayed via touch-sensitive display device 602, suchas display of lab result data room user interface 668 as depicted inFIGS. 6PA-6PB.

FIGS. 6PA-6PB depict first electronic device 600 displaying lab resultdata room user interface 668 via touch-sensitive display device 602 at asixteenth time after the fifteenth time. In some examples, lab resultdata room user interface 668 is displayed in response to user inputcorresponding to selection of representation 666 e in all health datauser interface 664 as depicted in FIG. 60A. In other examples, labresult data room user interface 668 is displayed in response to userinput corresponding to a notification representation in summary userinterface 614 indicating that lab results (e.g., and no other healthrecord types) have been updated. In other examples, lab result data roomuser interface 668 is displayed in response to searching for lab resultsusing search user interface 684 as depicted in FIG. 6TA and selecting anaffordance corresponding to lab result data room user interface 668 insearch results.

As depicted in FIG. 6PA, lab result data room user interface 668includes icon 668 a and title 668 b corresponding to and indicating thehealth record type “lab result.” In some examples, user interfaceelements corresponding to the health record type “lab result” include anicon similar to icon 668 a.

As depicted in FIG. 6PA, lab result data room user interface 668includes last updated affordance 668 c and A-to-Z affordance 668 d forswitching between views of lab result data room user interface 668. Forexample, user input corresponding to selection of last updatedaffordance 668 c causes lab result data room user interface 668 todisplay a first view, as depicted in FIGS. 6PA-6PB. Similarly, userinput corresponding to selection of A-to-Z affordance 668 d causes labresult data room user interface 668 to display a second view, asdepicted in FIG. 6Q.

As depicted in FIGS. 6PA-6PB, lab result data room user interface 668includes multiple regions (e.g., region 670 and region 672), each regioncorresponding to a different date that health records within the regionwere generated (e.g., collected, taken, or otherwise created by aclinical institution). In some examples, the multiple regions areordered by date, such that regions corresponding to more recent datesare before regions corresponding to later dates. For example, lab resultdata room user interface 668 includes region 670 (which is indicated tocorrespond to Mar. 29, 2019) (as depicted in FIG. 6PA) higher in a listthan (e.g., before) region 672 (which is indicated to correspond to Aug.15, 2019) (as depicted in FIG. 6PB).

In some examples, each region included in lab result data room userinterface 668 includes one or more representations of health records.For example, region 670 includes two representations of two separatehealth records: representation 670 b and representation 670 c. Foranother example, region 672 includes three representations:representation 672 b, representation 672 c, and representation 672 d.

In some examples, representations within a region are included in asub-region corresponding to a clinical institution associated with thehealth records. For example, representation 670 b and representation 670c are included in a sub-region that corresponds to XYZ Medical Center,indicating that health records corresponding to representation 670 b andrepresentation 670 c were received from (e.g., generated by) XYZ MedicalCenter. For another example, representation 672 b, representation 672 c,and representation 672 d are included in a sub-region that correspondsto ABC Urgent Care, indicating that the health records corresponding torepresentation 672 b, representation 672 c, and representation 672 dwere received from (e.g., generated by) ABC Urgent Care. Suchillustrates that lab result data room user interface 668 can includesrepresentations from multiple clinical institutions.

In some examples, representations of health records in lab result dataroom user interface 668 include an icon indicating a correspondinghealth record type (as discussed above). In some examples,representations of health records in lab result data room user interface668 include information corresponding to a respective health record. Forexample, information in 670 b includes the word “collected,” indicatingthat a corresponding health record was collected on the associated date(e.g., Mar. 29, 2019).

The information in representation 670 b further includes a graphillustrating a corresponding health record. The graph in representation670 b includes multiple indications of a value (e.g., “125 MG/DL”)included in the corresponding health record and a range defined for thevalue (e.g., 0 to 200, which is a minimum and maximum value). Themultiple indications include a textual indication (e.g., the text) and agraphical representation (e.g., the dot in the visual representation ofthe range). In some examples, the value is considered to meet particularcriteria (e.g., criteria related to whether the value is acceptable,such as criteria set by a governing body) when the value is within therange. In some examples, the range is included in the correspondinghealth record. In other examples, the range is known by the healthapplication, such as from being provided by a remote source (such as aclinical institution).

FIG. 6PA depicts representation 670 c including a graph illustrating acorresponding health record. The graph in representation 670 c includesmultiple indications of a value (e.g., “6.3%”) included in thecorresponding health record and a range defined for the value (e.g., 5.7to 6.3, which is a minimum and maximum value). The multiple indicationsinclude a textual indication (e.g., the text) and a graphicalrepresentation (e.g., the dot in the visual representation of therange). In some examples, the value is considered to meet particularcriteria (e.g., criteria related to whether the value is acceptable,such as criteria set by a governing body) when the value is within therange. In some examples, the range is included in the correspondinghealth record. In other examples, the range is known by the healthapplication, such as from being provided by a remote source (such as aclinical institution).

FIG. 6PB depicts representation 672 b including information from acorresponding health record. The information in representation 672 bincludes a single indication (e.g., a textual indication) of a value(e.g., “40%”) included in the corresponding health record and noindication of a range defined for the value. In some examples, theinformation in representation 672 b does not include a graph (and/or anindication of a range) because the health application is unable toidentify a range for the value (e.g., the corresponding health recorddid not include the range and/or an institution has not provided therange).

FIG. 6PB depicts representation 672 c including information from acorresponding health record. The information in representation 672 cincludes a single indication (e.g., a textual indication) of a value(e.g., “NEGATIVE”) included in the corresponding health record. In someexamples, the information in representation 672 b does not include agraph (and/or an indication of a range) because the value is less than aminimum number of possible values for the corresponding health record(in some examples, the minimum number of possible values is three (e.g.,binary values will not be graphed).

FIG. 6PB depicts representation 672 d including a graph illustrating acorresponding health record. The graph in representation 672 d includesmultiple indications of a value (e.g., “4.5 trillion”) included in thecorresponding health record and a range defined for the value (e.g.,5.32 to 5.72 trillion, which is a minimum and maximum value). Themultiple indications include a textual indication (e.g., the text) and agraphical representation (e.g., the dot in the visual representation ofthe range). In some examples, the value is considered to meet particularcriteria (e.g., criteria related to whether the value is acceptable,such as criteria set by a governing body) when the value is within therange. In some examples, the range is included in the correspondinghealth record. In other examples, the range is known by the healthapplication, such as from being provided by a remote source (such as aclinical institution). FIG. 6PB illustrates that some representationscan include graphs while other representations do not include a graph,even representations corresponding to the same health record type. Sucha result, in some examples, is due to some health records not includingranges and/or being binary values.

FIG. 6PA depicts first electronic device 600 receiving user input 669corresponding to A-to-Z affordance 668 d. In some examples, user input669 is received via touch-sensitive display device 602 and correspondsto a selection gesture (e.g., tap) on A-to-Z affordance 668 d. In otherexamples, other forms of selection can be used, such as a click using amouse. In some examples, user input 669 causes a different view of labresult data room user interface 668 to be displayed via touch-sensitivedisplay device 602, such as the A-to-Z view depicted in FIG. 6Q.

FIG. 6Q depicts first electronic device 600 displaying an A-to-Z view oflab result data room user interface 668 via touch-sensitive displaydevice 602 at a seventeenth time after the sixteenth time. In someexamples, the A-to-Z view is displayed in response to user inputcorresponding to selection of A-to-Z affordance 668 d in lab result dataroom user interface 668 as depicted in FIG. 6PA.

As depicted in FIG. 6Q, the A-to-Z view includes last updated affordance668 c and A-to-Z affordance 668 d for switching between views of labresult data room user interface 668. For example, user inputcorresponding to selection of last updated affordance 668 c causes labresult data room user interface 668 to display a first view, as depictedin FIGS. 6PA-6PB. Similarly, user input corresponding to selection ofA-to-Z affordance 668 d causes lab result data room user interface 668to display a second view, as depicted in FIG. 6Q.

As depicted in FIG. 6Q, the A-to-Z view includes a list of affordancesfor different lab results, each affordance corresponding to a differenttype of lab result. In some examples, the list of affordances arealphabetically ordered by each affordance's corresponding type of labresult (e.g., a cholesterol affordance (e.g., affordance 674 a) isbefore a creatine affordance (e.g., affordance 674 b)). In someexamples, each affordance in the list of affordances includes anindication regarding a number of health records associated with acorresponding type of lab result. For example, the “12” in affordance674 a indicates that the health system has received 12 health recordscorresponding to cholesterol.

FIG. 6Q depicts first electronic device 600 receiving user input 675corresponding to affordance 674 c. In some examples, user input 675 isreceived via touch-sensitive display device 602 and corresponds to aselection gesture (e.g., tap) on affordance 674 c. In other examples,other forms of selection can be used, such as a click using a mouse. Insome examples, user input 675 causes a different user interface to bedisplayed via touch-sensitive display device 602, such as hemoglobinuser interface 676 depicted in FIGS. 6RA-6RB.

FIGS. 6RA-6RB depict first electronic device 600 displaying hemoglobinuser interface 676 via touch-sensitive display device 602 at aneighteenth time after the seventeenth time. In some examples, hemoglobinuser interface 676 is displayed in response to user input correspondingto selection of affordance 674 c in lab result data room user interface668 as depicted in FIG. 6Q. In some examples, hemoglobin user interface676 is displayed in response to user input corresponding to selection ofaffordance 670 c in lab result data room user interface 668 as depictedin FIG. 6PA. In some examples, hemoglobin user interface 676 is a userinterface of the health application with information based on healthrecords corresponding to Hemoglobin A1C.

As depicted in FIG. 6RA, hemoglobin user interface 676 includes a graphwith data indicating values obtained from health records correspondingto Hemoglobin A1C throughout a year. For example, a first health recordcan indicate that results for a first Hemoglobin A1C test were 6.3%(e.g., the first health record corresponds to affordance 680 a), asecond health record can indicate that results for a second HemoglobinA1C test were 7.3% (e.g., the second health record corresponds toaffordance 680 b), and a third health record can indicate that resultsfor a third Hemoglobin A1C test were 6% (e.g., the third health recordcorresponds to affordance 680 c). With such health records, the graphincludes an indication for the first health record (e.g., 676 cc), thesecond health record (e.g., 676 ca), and the third health record (e.g.,676 cb). In some examples, the graph also includes representation 676cd, providing additional information regarding one of the health recordsin the graph. As depicted in FIG. 6RA, representation 676 cd relates tothe first health record. In some examples, representation 676 cd relatesto the first health record in response to user input on indication 676cc and/or selection of an affordance on a different user inter to causehemoglobin user interface 676 to be displayed, the affordancecorresponding to a health record associated with indication 676 cc(e.g., affordance 670 c as depicted in FIG. 6PA).

As depicted in FIG. 6RA, hemoglobin user interface 676 includes timescale affordances at the top indicating different time scales (e.g., “W”indicating a week, “M” indicating a month, “Y” indicating a year, and“5Y” indicating 5 years). As depicted FIG. 6RA, the time scaleaffordance indicating year is selected, causing the graph to indicatehealth records throughout a year. In some examples, selection of adifferent time scale affordance causes the graph to change to indicatehealth records detected throughout a selected time scale.

As depicted in FIG. 6RA, hemoglobin user interface 676 includes out ofrange affordance 678. Selection of out of range affordance 678 causesindications in the graph to be visually distinguished (e.g.,highlighted) that correspond to a value that is out of a defined range,as discussed above.

FIG. 6RA depicts first electronic device 600 receiving user input 681corresponding to affordance 680 a. In some examples, user input 681 isreceived via touch-sensitive display device 602 and corresponds to aselection gesture (e.g., tap) on affordance 680 a. In other examples,other forms of selection can be used, such as a click using a mouse. Insome examples, user input 681 causes a different user interface to bedisplayed via touch-sensitive display device 602, such as lab resultrecord user interface 682 depicted in FIG. 6SA.

FIG. 6SA depicts first electronic device 600 displaying lab resultrecord user interface 682 via touch-sensitive display device 602 at anineteenth time after the eighteenth time. In some examples, lab resultrecord user interface 682 is displayed in response to user inputcorresponding to selection of affordance 680 a in hemoglobin userinterface 676 as depicted in FIG. 6RA. In some examples, lab resultrecord user interface 682 includes detailed information regarding aparticular health record. In some examples, the detailed informationincludes a date when the particular health record was collected, a datewhen the particular health record was received by the healthapplication, alternate names for the particular health record (e.g., asidentified from either a remote source or other health recordsassociated with the account of the health application), a clinicalinstitution associated with the particular health record, and otherinformation included in the particular health record.

FIGS. 6SB-6SC depict first electronic device 600 displaying XYZ medicalcenter user interface 698 via touch-sensitive display device 602. Insome examples, XYZ medical center user interface 698 is displayed inresponse to user input corresponding to selection of first healthrecords affordance 636 in the health records region of summary userinterface 614 as depicted in FIG. 6DC.

As depicted in FIGS. 6SB-6SC, XYZ medical center user interface 698includes multiple regions (e.g., regions for different days), eachregion corresponding to a different date that health records within theregion were generated (e.g., collected, taken, or otherwise created by aclinical institution). In some examples, the multiple regions areordered by date, such that regions corresponding to more recent datesare before regions corresponding to later dates. For example, XYZmedical center user interface 698 includes a region corresponding toMar. 29, 2019, (as depicted in FIG. 6SB) higher in a list than (e.g.,before) a region corresponding to Nov. 2, 2018 (as depicted in FIG.6SC).

In some examples, each region included in XYZ medical center userinterface 698 includes one or more sub-regions, each sub-regioncorresponding to a different health records type (e.g., allergies,medications, etc.) within the sub-region. In some examples, multiplesub-regions are ordered alphabetically (e.g., allergies beforemedications) (not illustrated).

In some examples, each sub-region included in XYZ medical center userinterface 698 includes one or more representations of health records.For example, sub-region 698 a includes four representations of fourseparate health records, such as representation 670 b (as also depictedand described in FIG. 6PA), representation 670 c (as also depicted anddescribed in FIG. 6PA), representation 698 b (similar to 672 b asdepicted and described in FIG. 6PB, but from XYZ Medical Center insteadof ABC Urgent Care), and representation 698 c (similar to 672 c asdepicted and described in FIG. 6PB, but from XYZ Medical Center insteadof ABC Urgent Care). FIGS. 6SB-6SC illustrate that some representationscan include graphs while other representations do not include a graph,even representations corresponding to the same health record type. Sucha result, in some examples, is due to some health records not includingranges and/or being binary values. While FIGS. 6SB-6SC depict a userinterface for a single clinical institution, it should be recognizedthat similar techniques can be used for a user interface withrepresentations for health records from multiple clinical institutions.

FIG. 6TA depicts first electronic device 600 displaying search userinterface 684 via touch-sensitive display device 602 at a twentieth timeafter the nineteenth time. In some examples, search user interface 684is displayed in response to user input corresponding to selection ofsearch affordance 642 b in any user interface of health application,such as summary user interface 614.

As depicted in FIG. 6TA, search user interface 684 includes search area684 a for inserting a search query to use to search the healthapplication. For example, when first electronic device 600 receives userinput corresponding to a string (e.g., a user types in a string using akeyboard) while focusing on search area 684 a (e.g., an insertion markeris located within search area 684 a) and a request to perform a search,first electronic device 600 searches data associated with the healthapplication based on the string, as depicted in FIG. 6U and furtherdiscussed below.

As depicted in FIG. 6TA, search user interface 684 includes four groupsof affordances: shared health data affordances 684 b, health categoriesaffordances 684 c, health records affordances 684 d, and health contentaffordances 684 g. In some examples, search user interface 684 includesless groups of affordances, such as not including shared health dataaffordances 684 b when first electronic device 600 is not receivingshared health data from another device.

In some examples, affordances of shared health data affordances 684 brelate to other accounts for which are linked with the accountassociated with the health application. In one example, linking includesa connection between the two accounts such that health data recorded forone account is sent to the other account. For example, FIG. 6TA depictsthat shared health data affordances 684 b includes affordance 684 ba. Insome examples, affordance 684 ba relates to an account associated with“Little Appleseed” such that selection of affordance 684 ba causesdisplay of a user interface for the account associated with “LittleAppleseed” (e.g., a user interface allowing a user to view health dataassociated with the account associated with “Little Appleseed”), asdepicted in FIG. 6XA and discussed below.

In some examples, affordances of health categories affordances 684 crelate to categories of health data types. In particular, healthcategories affordances 684 c represents a hierarchy of health data,allowing a user to navigate to particular health data through one ormore user inputs. For example, health categories affordances 684 cincludes affordance 684 ca corresponding to activity health data type(e.g., a type of health data corresponding to activity). In someexamples, the activity health data type corresponds to health datastored by an activity application. For another example, healthcategories affordances 684 c includes affordance 684 ck corresponding tovitals health data type (e.g., a type of health data corresponding tovitals). In some examples, the vitals health data type corresponds tohealth data stored by a vitals application.

In some examples, selection of an affordance of health categoriesaffordances 684 c causes a user interface of the health application tobe displayed, the user interface including health data associated with arespective health data type, as depicted in FIGS. 6V-6W and discussedbelow.

In some examples, affordances of health records affordances 684 d relateto categories of health records, as discussed above. For example, healthrecords affordances 684 d represents a hierarchy of health records,allowing a user to navigate to a particular health record through one ormore user inputs. For example, health records affordances 684 d includesaffordance 684 de corresponding to lab results (e.g., a type of healthrecord). In some examples, selection of affordance 684 de causes a userinterface to be displayed, the user interface including lab resultshealth records. Health records affordances 684 d also includeaffordances related to clinical institutions (e.g., affordance 684 h).Selection of an affordance related to a clinical institution causes auser interface of the health application to be displayed, the userinterface including heath records gathered by the clinical institution.Selection of an affordance related to all accounts (e.g., affordance 684dj) causes a user interface of the health application to be displayed,the user interface including all heath records.

As depicted in FIG. 6TB, search user interface 684 includes affordance684 e for viewing clinical documents. Selection of affordance 684 ecauses a user interface of the health application to be displayed, theuser interface including clinical documents. As depicted in FIG. 6TB,search user interface 684 includes affordance 684 f for viewingunreadable data (e.g., data that the health application (or a processrelated to the health application) is unable to parse (e.g., interpretor read). Selection of affordance 684 f causes a user interface of thehealth application to be displayed, the user interface includingrepresentations of health records that were unable to be parsed by thehealth application (or a process related to the health application).

In some examples, affordances of health content affordances 684 g relateto links to other health content. For example, health contentaffordances 684 g includes an affordance to view educational content.Selection of such an affordance causes a user interface of the healthapplication to be displayed, the user interface including educationalcontent. For another example, health content affordances 684 g includesan affordance to view highlights, which were discussed above. Selectionof such an affordance causes a user interface of the health applicationto be displayed, the user interface including one or more highlightrepresentations.

FIG. 6U depicts first electronic device 600 displaying search userinterface 684 via touch-sensitive display device 602 at a twenty-firsttime after the twentieth time. In some examples, search user interface684 (as depicted in FIG. 6U) is displayed in response to a userrequesting to search for a string entered into search area 684 a. Forexample, FIG. 6U depicts that a user has entered “BLOOD PRESS” intosearch area 684 a, causing search results to be displayed correspondingto a search for “BLOOD PRESS” using the health application. In someexamples, the user requesting to search for the string causes the searchresults to replace (e.g., cease to display) the four groups ofaffordances in search user interface 684 depicted in FIGS. 6TA-6TB.

In some examples, the search results include data from differentsources. For example, first search result 684 h includes health data(e.g., health data detected by first electronic device 600 or anotherdevice linked to either first electronic device 600 or the accountassociated with the health application). As depicted in FIG. 6U, firstsearch result 684 h includes a representation of blood pressure detectedfor a user associated with the account. For another example, secondsearch result 684 i includes health record data (e.g., health recordsreceived by first electronic device 600 from, for example, a clinicalinstitution). As depicted in FIG. 6U, second search result 685 iincludes blood pressure that was included in a health record.

In some examples, the search results include categories of highlightsdetermined to be related to the string. For example, FIG. 6U depictsthat the search results include heart highlights affordance 685 j a(e.g., an affordance related to highlights associated with the heart)and vitals highlights affordance 685 jb (e.g., an affordance related tohighlights associated with vitals). In some examples, selection of ahighlight affordances causes a user interface of the health applicationto be displayed, the user interface including one or more highlightrepresentations related to the respective category of highlights.

In some examples, the search results include categories of health datadetermined to be related to the string (684 k). Such categoriescorrespond to health categories affordances 684 c discussed above. Forexample, FIG. 6U depicts that the search results include heart categoryaffordance 684 ka, vitals affordance 684 kb, and clinical vitalsaffordance 684 kc. The categories of health data represents a hierarchyof health records, allowing a user to navigate to a particular healthrecord through one or more user inputs. For example, selection of anaffordance corresponding to a category of health data causes a userinterface to be displayed, the user interface including health recordscorresponding to the category.

FIG. 6V depicts first electronic device 600 displaying activity userinterface 686 via touch-sensitive display device 602 at a twenty-secondtime after the twenty-first time. In some examples, activity userinterface 686 is displayed in response to user input corresponding toselection of affordance 684 ca in search user interface 684.

As depicted in FIG. 6V, activity user interface 686 includesrepresentations of health data related to activity for the accountassociated with the health application. For example, activity userinterface 686 includes representation 686 a with heart rate data duringstrength training.

FIG. 6W depicts first electronic device 600 displaying vitals userinterface 688 via touch-sensitive display device 602 at a twenty-thirdtime after the twenty-second time. In some examples, vitals userinterface 688 is displayed in response to user input corresponding toselection of affordance 684 ck in search user interface 684.

As depicted in FIG. 6W, vitals user interface 688 includesrepresentations of health data related to vitals for the accountassociated with the health application. For example, activity userinterface 686 includes representation 688 a with heart rate data duringstrength training. Representation 688 a is an example that health dataincluded in one category (e.g., vitals) can be included in anothercategory (e.g., activity). Such a result is due to health data havingmultiple categories for which they are associated. For example, heartrate data during strength training, as depicted in FIGS. 6V-6W, isassociated with both activity and vitals. In some examples, health datahas a primary and a secondary health category.

FIGS. 6XA-6XB depict first electronic device 600 displaying child searchuser interface 690 via touch-sensitive display device 602 at atwenty-fourth time after the twenty-third time. In some examples, childsearch user interface 690 and user interfaces navigated from affordancesincluded in child search user interface 690 are read-only (as comparedto search user interface 684, which, in some examples, allows a user toadd/remove/edit data when navigating to data associated with the accountof the health application). In some examples, child search userinterface 690 is displayed in response to user input corresponding toselection of affordance 684 ba in search user interface 684.

In some examples, child search user interface 690 is a version of searchuser interface 684 for an account linked to the account associated withthe health application. As depicted in FIGS. 6XA-6XB, child search userinterface 690 includes search area 692 a (similar to search area 684 ain search user interface 684, except that search area 692 a searchesdata corresponding to Little Appleseed instead of the account associatedwith the health application), health categories affordances 692 b(similar to health categories affordances 684 c in search user interface684, except that health categories affordances 692 b is associated withdata corresponding to Little Appleseed instead of the account associatedwith the health application), health records affordances 692 c (similarto health records affordances 684 d in search user interface 684, exceptthat health records affordances 692 c is associated with datacorresponding to Little Appleseed instead of the account associated withthe health application), and health content affordances 692 e (similarto health content affordances 684 g in search user interface 684). Insome examples, child search user interface 690 does not include sharedhealth data affordances (e.g., shared health data affordances 684 ba).In other examples, child search user interface 690 includes sharedhealth data affordances for devices that are linked to LittleAppleseed's account.

FIG. 6Y depicts first electronic device 600 displaying activity userinterface 694 via touch-sensitive display device 602 at a twenty-fifthtime after the twenty-fourth time. In some examples, activity userinterface 694 is displayed in response to user input corresponding toselection of activity affordance in child search user interface 690.

As depicted in FIG. 6Y, activity user interface 694 includesrepresentations of health data related to activity for LittleAppleseed's account (e.g., as indicated by indication 694 a). Forexample, activity user interface 694 includes representation 694 c withheart rate data during strength training for Little Appleseed.

FIG. 6Z depicts first electronic device 600 displaying vitals userinterface 696 via touch-sensitive display device 602 at a twenty-sixthtime after the twenty-fifth time. In some examples, vitals userinterface 696 is displayed in response to user input corresponding toselection of vitals affordance in child search user interface 690.

As depicted in FIG. 6Z, vitals user interface 696 includesrepresentations of health data related to vitals for Little Appleseed'saccount (e.g., as indicated by indication 696 a). For example, vitalsuser interface 696 includes representation 696 c with heart rate dataduring strength training for Little Appleseed. Representation 696 c isan example that health data included in one category (e.g., vitals) canbe included in another category (e.g., activity). Such a result is dueto health data having multiple categories for which they are associated.For example, heart rate data during strength training, as depicted inFIGS. 6Y-6Z, is associated with both activity and vitals. In someexamples, health data has a primary and a secondary health category.

FIGS. 7A-7B are a flow diagram illustrating a method for managingnotifications using an electronic device in accordance with someembodiments. Method 700 is performed at a device (e.g., 100, 300, 500,600, 606) with a display device. Some operations in method 700 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for managingnotifications. The method reduces the cognitive burden on a user forviewing and acting on notifications, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to view and act on notifications faster and moreefficiently conserves power and increases the time between batterycharges.

The electronic device displays (702), via the display device, a firstinstance (e.g., 614, as depicted in FIG. 6DA) of a first user interfaceincluding a first notification (e.g., 616, 618, 620) (e.g., anotification affordance) that, when selected, causes display of a firstset of data (e.g., 644) (e.g., notification data, data generated orreceived (e.g., from an external device) at a first time; health data;sensor data; biometric data; physical activity data; clinical data).

In some embodiments, the first notification includes a first visualproperty (704) (e.g., a color (e.g., depicted as pattern in header of616, which includes 616 b and 616 c, pattern in header of 618, whichincludes 618 a, 618 b and 618 c, and pattern in header of 620, whichincludes 620 a, 620 b, and 620 c) (e.g., a foreground color, abackground color, inclusion (or exclusion) of a respective icon). Insome embodiments, in accordance with (706) a determination that thefirst set of data corresponds to (e.g., was generated by) a firstapplication, the first visual property has a first value (e.g., blue).In some embodiments, in accordance with (708) a determination that thefirst set of data corresponds to a second application, the first visualproperty has a second value (e.g., red) different from the first value.

Specifying a visual quality (e.g., color) of a notification based on thecorresponding application provides the user with feedback that helpsidentify the application. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

After displaying the first instance of the first user interface, theelectronic device displays (710) (e.g., in response to an inputcorresponding to a request to display the first user interface) a secondinstance (e.g., 614, as depicted in FIG. 6G) of the first userinterface.

In accordance with (712) a determination that a set of interactioncriteria (a set of criteria relating to whether the first set of datahas been interacted with (e.g., via selection of the firstnotification)) are met, the set of interaction criteria including acriterion that is met when the first set of data has been displayed(e.g., displayed in the first instance of the first user interface,displayed in a subsequent instance of the first user interface,displayed on the electronic device, displayed on a second electronicdevice that receives the same notifications as the electronic device(e.g., because both are associated with the same user account)), and inaccordance with a determination that a first set of removal criteria(e.g., a set of criteria that govern display of a notification thatcorresponds to data that has been interacted with) are not met, thefirst set of removal criteria including a first criterion that is basedon a first period of time (e.g., a period time that must be exceeded tomeet the first criterion; a period of time determined from when thefirst set of data was received or generated; a period of time determinedfrom when a notification corresponding to the first set of data wasfirst displayed; a non-zero period of time), the second instance of thefirst user interface includes the first notification (FIG. 6G-6H).

In accordance with (714) a determination that the set of interactioncriteria are met and in accordance with a determination that the firstset of removal criteria are met, the second instance of the first userinterface does not include the first notification (FIG. 6G-6H).

In accordance with (716) a determination that the set of interactioncriteria are not met and in accordance with a determination that asecond set of removal criteria (e.g., a set of criteria that governdisplay of a notification that corresponds to data that has not beeninteracted with) are not met, the second set of removal criteriaincluding a second criterion that is based on a second period of time(e.g., a period time that must be exceeded to meet the second criterion;a period of time determined from when the first set of data was receivedor generated; a period of time determined from when a notificationcorresponding to the first set of data was first displayed) that isgreater than the first period of time, the second instance of the firstuser interface includes the first notification (FIG. 6G-6H). In someembodiments, the second period of time is less than the first period oftime.

In accordance with (718) a determination that the set of interactioncriteria are not met and in accordance with a determination that thesecond set of removal criteria are met, the second instance of the firstuser interface does not include the first notification (FIG. 6G-6H). Insome embodiments, a notification is displayed (or redisplayed) in afirst user interface for a period of time that varies based on whetherthe notification has been interacted with. In some embodiments, anotification that has not been interacted with is displayed for a periodof time that is greater than for a notification that has been interactedwith.

Displaying the first notification based on whether the set ofinteraction criteria and the sets of removal criteria are met enablesthe user to view relevant notifications without providing unwantednotifications. Performing an operation when a set of conditions has beenmet without requiring further user input enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, prior to displaying the first instance of the firstuser interface, the electronic device receives, from an external device(e.g., a smart watch that includes one or more sensors (e.g., biometricsensors)), a second set of data, wherein the first set of datacorresponds to the second set of data (e.g., 610). In some embodiments,the external device is in a paired relationship with the electronicdevice (e.g., both devices are associated with the same user account andhave a persistent relationship). In some embodiments, the second set ofdata is the first set of data. In some embodiments, the second set ofdata is included in the first set of data. In some embodiments, thefirst set of data is derived from (e.g., calculated based on) the secondset of data. In some embodiments, the second set of data is sensor datafrom one or more sensors of the external device. In some embodiments,the second set of data includes clinical health data (e.g., 604 b)(e.g., medical records from a health institution; test results from aclinical testing lab).

In some embodiments, the electronic device includes a set of one or moresensors (e.g., biometric sensors). In some embodiments, prior todisplaying the first instance of the first user interface, theelectronic device receives (e.g., detecting), via the set of one or moresensors, a third set of data (e.g., 604 a). In some embodiments, thefirst set of data corresponds to the third set of data. In someembodiments, the third set of data is the first set of data. In someembodiments, the third set of data is included in the first set of data.In some embodiments, the first set of data is derived from (e.g.,calculated based on) the third set of data. In some embodiments, priorto displaying the first instance of the first user interface, theelectronic device displays a second user interface (e.g., any userinterface other than the summary tab of the health application, such asa lock screen) including a second notification corresponding to thethird set of data. In some embodiments, the second user interface isdifferent from the first user interface. In some embodiments, the secondnotification includes the same content as the first notification.

In some embodiments, the first notification is included in a first listof notifications. In some embodiments, the first list of notificationsis ordered based on chronological or reverse chronological order (e.g.,based on an initial notification issuance time; based on a time whendata that is displayed when a respective notification is selected wasgenerated or received) (e.g., FIG. 6DA).

Ordering the first list based on chronological or reverse chronologicalorder structures provides the user with feedback about the sequence inwhich the notifications were generated. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while displaying the first notification (e.g., inthe first instance or the second instance of the first user interface),the electronic device receives a first input (e.g., 615) correspondingto selection of the first notification. In some embodiments, in responseto receiving the first input, the electronic device displays, via thefirst display device, a second user interface (e.g., 644) (e.g., thatincludes the first set of data. In some embodiments, the first set ofdata corresponds to a first application and the second user interfaceincludes additional data and/or information from the first application.

In some embodiments, the first set of data corresponds to a first datatype (e.g., biometric data, sensor data). In some embodiments, thesecond user interface includes: a first affordance that, when selected,causes display of a first value (e.g., a first average) of the firstdata type; and a second affordance that, when selected, causes displayof a second value (e.g., a second average that based on a differentfilter (e.g., a time filter, a source filter) than the first average) ofthe first data type that is different from the first value (e.g.,average and daily average affordances in 644).

Note that details of the processes described above with respect tomethod 700 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described below/above. For example, methods 800,900, 1000, 1100, and 1400 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 700. For brevity, these details are not repeated below.

FIGS. 8A-8B are a flow diagram illustrating a method for managingdisplay of health-related information using an electronic device inaccordance with some embodiments. Method 800 is performed at a device(e.g., 100, 300, 500, 600) with a display device. Some operations inmethod 800 are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 800 provides an intuitive way for managingdisplay of health-related information. The method reduces the cognitiveburden on a user for viewing health-related information, therebycreating a more efficient human-machine interface. For battery-operatedcomputing devices, enabling a user to view health-related informationfaster and more efficiently conserves power and increases the timebetween battery charges.

The electronic device receives (802) first health data (e.g., physicalactivity performed by a user; data detected via one or more biometricsensors) (e.g., see 626 b). In some embodiments, the first health datais received over a period of time. In some embodiments, the first healthdata is received together, as a set.

The electronic device receives (804) a request (e.g., 613) (e.g., arequest to view a summary tab of a health application, such as a usertapping on an icon for the health application or a user tapping on anaffordance for the summary tab) to display a first user interface (e.g.,614).

In response to receiving the request, the electronic device displays(806), via the display device, the first user interface (e.g., 614)including a first region (e.g., the favorites region in 614) (808)(e.g., favorites section). The first user region, in accordance with(812) a determination that a type of data (e.g., activity, environmentalnoise, etc.) corresponding to the first health data has been identifiedby user input (e.g., a user has favorited the type of data), includes afirst representation (e.g., 626 a) of the first health data (e.g., anumber of steps made during a current day). The first user region, inaccordance with (814) a determination that the type of datacorresponding to the first health data has not been identified by userinput (e.g., the user has not favorited the type of data), does notinclude the representation of the first health data.

In response to receiving the request, the electronic device displays(806), via the display device, the first user interface including asecond region (e.g., the highlights region in 614) (810) (e.g.,highlights section). The second region, in accordance with (816) adetermination that a first set of highlight criteria are met (e.g., asystem determines that the representation corresponding to the healthdata should be displayed to a user), includes a second representation(e.g., 630, 632 652, 654, 656, 658, 660, 662) of the first health datadifferent from the first representation (e.g., a graphicalrepresentation comparing health data for a first health metric over afirst time period with health data for the first health metric over asecond time period different from the first time period). In someembodiments, representations that are displayed in the second region arenot user-customizable/user-selectable. In some embodiments,representations that are displayed in the second region include acomparison of the health data to health data that corresponds to adifferent period of time than the period time of the health data. Thesecond region, in accordance with (818) a determination that the firstset of highlight criteria are not met (e.g., a system determines thatthe representation corresponding to the health data should not bedisplayed to a user), does not include the second representation of thefirst health data.

Including the second representation of the first health data based onthe first set of highlight criteria being met enables the device todisplay relevant information and to avoid using display space when theinformation is not relevant. Performing an operation when a set ofconditions has been met without requiring further user input enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the health data includes health data for a firstplurality of time periods (e.g., days, weeks, months). In someembodiments, the first representation of the health data includes: afirst indication (e.g., a text indication, a graphical indication; anindication of a first metric (e.g., steps, miles, calories)) of thehealth data corresponding to a first time period (e.g., today) of thefirst plurality of time periods; and a second indication (e.g., a textindication, a graphical indication) of the health data corresponding toa second time period (e.g., yesterday) of the first plurality of timeperiods that is different from the first time period. In someembodiments, the first representation includes a bar graph having valuesfor today compared to values for yesterday (e.g., 632).

Providing different indications for different time periods provides theuser with feedback about the stored data that corresponds to therespective time periods. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the first time period of the first plurality oftime periods corresponds to a specific instance of a recurring timeinterval (e.g., specific hours of a day, specific day in a week or amonth). In some embodiments, the second time period of the firstplurality of time periods is a plurality of instances. In someembodiments, all of the instances of the recurring time intervalavailable in the health data) of the recurring time interval (e.g.,multiple Mondays of weeks; multiple mornings of days). In someembodiments, the first indication is a value of a health metric for theMondays of a week and the second indication is an average value of thehealth metric for all Mondays (e.g., 662).

In some embodiments, the health data includes health data for a secondplurality of time periods (e.g., days, weeks, months). In someembodiments, the first representation of the health data includes athird indication of the health data corresponding to the frequency(e.g., as a ratio, as a percentage, as a fraction (e.g., 4 days out ofthe last week)) of the occurrence of a first health event (e.g., ahealth-related event) within the second plurality of time periods (e.g.,a day, a week, a year) (e.g., 654).

In some embodiments, the health data includes health data for a thirdplurality of time periods (e.g., days, weeks, months). In someembodiments, the first representation of the health data includes: afourth indication of an average value of the health data for the thirdplurality of time periods (e.g., an average for the week); a fifthindication corresponding to the value of the health data for a firsttime period of the third plurality of time periods (e.g., a day withinthe week); and a sixth indication corresponding to the value of thehealth data for a second time period of the third plurality of timeperiods (e.g., a day within the week) that is different from the firsttime period of the plurality of time periods (e.g., 652).

In some embodiments, the first representation includes a seventhindication corresponding to a first physical activity tracking session(e.g., a first workout). In some embodiments, the first representationincludes an eighth indication corresponding to a second physicalactivity tracking session. In some embodiments, the first and secondphysical activity tracking sessions are different types of workouts(e.g., running and swimming). In some embodiments, the first physicalactivity tracking session and the second physical activity trackingsession correspond to the same time period (e.g., same day, same week,same month). In some embodiments, a ninth indication of the health data(e.g., total calories burned, an average pace) that is based on thefirst physical activity tracking session and the second physicalactivity tracking session (e.g., 658).

Displaying an indication of the health data that is based on the firstand second physical activity tracking sessions provides the user withfeedback, using the indication, about both the sessions. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first set of highlight criteria includes acriterion that is based on a factor selected from the group consistingof: a relationship (e.g., a mathematical relationship (e.g., adifference)) between a first portion (e.g., a portion corresponding to afirst time period (e.g., a day)) of the health data and a second portion(e.g., a portion corresponding to a second time period (e.g., a week))of the health data, a degree of user interaction with the health data,and a duration of time in which a representation (e.g., anyrepresentation) of the health data has been displayed (e.g., on theelectronic device).

In some embodiments, the first representation is included in a firstlist of representation. In some embodiments, the first list ofrepresentations is ordered based on the types of data of the health data(e.g., physical activity data is grouped together; heart-related data isgrouped together) (e.g., 660).

Note that details of the processes described above with respect tomethod 800 (e.g., FIGS. 8A-8B) are also applicable in an analogousmanner to the methods described below/above. For example, methods 700,900, 1000, 1100, and 1400 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 800. For brevity, these details are not repeated below.

FIGS. 9A-9B is a flow diagram illustrating a method for managing displayof clinical health record representations using an electronic device inaccordance with some embodiments. Method 900 is performed at a device(e.g., 100, 300, 500, 600, 606) with a display device. Some operationsin method 900 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way for managingdisplay of clinical health record representations. The method reducesthe cognitive burden on a user for accessing clinical health records,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to access clinicalhealth records faster and more efficiently conserves power and increasesthe time between battery charges.

The electronic device receives (902) clinical health record datacorresponding to a particular health institution (e.g., 672 a, XYZMedical Center in 698). The electronic device receives (904) a request(e.g., 667, tap first health records affordance 636 in summary userinterface 614) (e.g., a request to view all clinical health records forXYZ Medical Center) to display a first user interface (e.g., 668, 698).

In response to receiving the request, the electronic device displays(906), via the display device, the first user interface (e.g., 668,698). The first user interface includes a first region (e.g., 672, 698a) (908) corresponding to a first type of clinical health record (e.g.,668 b, 698 a, a lab results region). The first region includes, inaccordance with (912) a determination that a first clinical healthrecord of the first type of clinical health record fails to meet a firstset of graphing criteria (e.g., the first clinical health record either(1) does not include a range for the first clinical health record or (2)includes binary information (which, in some examples, does not achievebenefit from graphing)), a first textual representation (e.g., 672 b,672 c, 698 b, 698 c) for the first clinical health record based on theclinical health record data, wherein the first user interface does notinclude a graphical representation (e.g., a non-textual graphicalrepresentation) for the first clinical health record. The first regionincludes, in accordance with (914) a determination that the firstclinical health meets the first set of graphing criteria (e.g., thefirst clinical health record includes a range for the first clinicalhealth record and includes non-binary information (which, in someexamples, achieves benefit from graphing)), a first graphicalrepresentation (e.g., 672 d in 668) (e.g., 670 b and 670 c in 698) forthe first clinical health record based on the clinical health recorddata.

In response to receiving the request, the electronic device displays(906), via the display device, the first user interface including asecond region (e.g., a different date range in 668, the medicationsregion in 698) (910) corresponding to a second type of clinical healthrecord (e.g., medications region). The second region includes, inaccordance with (916) a determination that a second clinical healthrecord of the second type of clinical health record fails to meet thefirst set of graphing criteria (e.g., the second clinical health recordeither (1) does not include a range for the second clinical healthrecord or (2) includes binary information (which, in some examples, doesnot achieve benefit from graphing)), a second textual representation forthe second clinical health record based on the clinical health recorddata, wherein the user interface does not include a graphicalrepresentation for the second clinical health record. The second reasonincludes, in accordance with (918) a determination that the secondclinical health record meets the first set of graphing criteria (e.g.,the second clinical health record includes a range for the secondclinical health record and includes non-binary information (which, insome examples, achieves benefit from graphing)), a second graphicalrepresentation for the second clinical health record based on theclinical health record data.

Displaying textual representations or graphical representations forhealth records provides the user with feedback about whether the healthrecord meets the graphing criteria and enables the user to more quicklyand efficient access information related to the record. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first set of graphing criteria are met (e.g.,the first set of graphing criteria includes a criterion that is met whenthe clinic health record includes a range for the clinical healthrecord) for a respective clinical health record when the respectiveclinical health record (e.g., the first clinical health record)corresponds to health data that includes a range of data (e.g., aminimum and maximum value that defines a range, where a data valuecorresponding to the respective clinical health record is considered tomeet particular criteria (e.g., criteria related to whether the datavalue is acceptable, such as criteria set by a governing body)) (e.g.,670 b, 670 c).

In some embodiments, the first set of graphing criteria are not met(e.g., the first set of graphing criteria includes a criterion that ismet when the clinic health record includes non-binary numeric data) fora respective clinical health record when the respective clinical healthrecord (e.g., the first clinical health record) corresponds to healthdata that is binary (e.g., having binary states (positive or negative;up or down; prescribed or not prescribed)) (e.g., 698 c).

In some embodiments, the first region includes a plurality ofrepresentations (e.g., textual representations) of clinical healthrecords. In some embodiments, the plurality of representations isordered primarily by a date (e.g., chronological by the date, reversechronologically by the date) and secondarily by a health record typeassociated with each clinical health record of each representation ofthe plurality of representations. In some embodiments, record typesinclude medications, lab results, symptoms, ailments, treatments.

Ordering the representations by date first, then by health record typeprovides the user with feedback about the corresponding date order ofthe records and the type of record. Providing improved visual feedbackto the user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first region includes a second plurality ofrepresentations (e.g., textual representations) of clinical healthrecords. In some embodiments, the second plurality of representations isordered primarily by a health record type and secondarily by a date(e.g., chronological by the date, reverse chronologically by the date)associated with each clinical health record of each representation ofthe second plurality of representations. In some embodiments, healthrecord types include medications, lab results, symptoms, ailments,treatments.

Ordering the representations by health record type first, then by dateprovides the user with feedback about the corresponding type of recordand the date order of the records. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first region includes a third plurality ofrepresentations (e.g., textual representations) of clinical healthrecords that each correspond to a clinical health record that isassociated with a first date (e.g., a date of when the record wasreceived (e.g., received by the electronic device)) and a second date(e.g., a date corresponding to a health event (e.g., when a test wasperformed, when a prescription was written) of the clinical healthrecord) different from the first date. In some embodiments, the thirdplurality of representations is ordered by, in accordance with adetermination that the first user interface is a user interface of afirst interface type (e.g., a summary user interface), the first date.In some embodiments, the third plurality of representations is orderedby, in accordance with a determination that the first user interface isa user interface of a second interface type (e.g., a user interface fora specific type of health data) different from the first interface type,the second date.

Note that details of the processes described above with respect tomethod 900 (e.g., FIGS. 9A-9B) are also applicable in an analogousmanner to the methods described below/above. For example, methods 700,800, 1000, 1100, and 1400 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 900. For brevity, these details are not repeated below.

FIGS. 10A-10B is a flow diagram illustrating a method for managingdisplay of clinical health record representations using an electronicdevice in accordance with some embodiments. Method 1000 is performed ata device (e.g., 100, 300, 500, 600) with a display device. Someoperations in method 1000 are, optionally, combined, the orders of someoperations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 1000 provides an intuitive way for managingdisplay of clinical health record representations. The method reducesthe cognitive burden on a user for accessing clinical health record,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to access clinicalhealth record faster and more efficiently conserves power and increasesthe time between battery charges.

The electronic device receives (1002) clinical health record data,including: first clinical health record data corresponding to a firsttype of clinical health record (e.g., medication); and second clinicalhealth record data corresponding to a second type of clinical healthrecord (e.g., lab results) (e.g., 668). The electronic device receives(1004) a request (e.g., a request (e.g., 667, to view all clinicalhealth records for a health record type) to display a first userinterface (e.g., 668).

In response to receiving the request, the electronic device displays(1006), via the display device, the first user interface (e.g., 668),including a first representation (e.g., 674 c), based on the firstclinical health record data, for a first clinical health record of thefirst type of clinical health record (e.g., an Acetaminophen healthrecord (where the type of clinical health record is a medicine)).

While displaying the first user interface, the electronic devicereceives (1008) first user input (e.g., 675) corresponding to selectionof the first representation.

In response to receiving the first user input, the electronic devicedisplays (1010), via the display device, a second user interface (e.g.,676) (e.g., an Acetaminophen user interface with representations fordifferent health records corresponding to Acetaminophen). The seconduser interface includes a second representation (e.g., 680 a) (1012),based on the first clinical health record data, for the first clinicalhealth record of the first type of clinical health record, wherein thesecond representation is different from the first representation (e.g.,a more-detailed representation for the Acetaminophen health record). Thesecond user interface includes a third representation (e.g., 680 b)(1014), based on the first clinical health record data, for a secondclinical health record of the first type of clinical health record,wherein the third representation is different from the secondrepresentation and the second clinical health record of the first typeis different from the first clinical health record (e.g., amore-detailed representation of another Acetaminophen health record) ofthe first type.

While displaying the second user interface, the electronic devicereceives (1016) second user input (e.g., 681) corresponding to selectionof the third representation.

In response to receiving the second user input, the electronic devicedisplays (1018), via the display device, a third user interface (e.g.,682) (e.g., an Acetaminophen user interface with a detailedrepresentation for a particular Acetaminophen record), including afourth representation, based on the first clinical health record data,for the first clinical health record of the first type of clinicalhealth record (e.g., a most-detailed representation for theAcetaminophen health record), wherein the fourth representation isdifferent from the first representation, and wherein the fourthrepresentation is different from the second representation.

In some embodiments, the request to display the first user interface isreceived while displaying, via the display device, a fourth userinterface (e.g., FIG. 12AA) that includes a fifth representation, basedon the second clinical health record data, for a second clinical healthrecord of the second type of clinical health record (e.g., a Cholesterolhealth record (where the type of clinical health record is a labresult)).

In some embodiments, the fourth user interface includes a plurality ofrepresentations (e.g., representations of clinical health records of thefirst type and/or second type) of clinical health records. In someembodiments, the plurality of representations is ordered primarily by adate (e.g., chronological by the date, reverse chronologically by thedate) and secondarily by a health record type associated with eachclinical health record of each representation of the plurality ofrepresentations. In some embodiments, health record types includemedications, lab results, symptoms, ailments, treatments.

Ordering the representations by date first, then by health record typeprovides the user with feedback about the corresponding date order ofthe records and the type of record. Providing improved visual feedbackto the user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the second user interface includes a secondplurality of representations (e.g., representations of clinical healthrecords of the first type and/or second type) of clinical healthrecords. In some embodiments, the second plurality of representationsordered by a date (e.g., chronological by the date, reversechronologically by the date).

Ordering the representations by health record type first, then by dateprovides the user with feedback about the corresponding type of recordand the date order of the records. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in accordance with a first set of graphic criteriais met, the first representation includes a graphical indication of thefirst clinical health record (e.g., a graph of the health data in theclinical health record). In some embodiments, the first set of graphiccriteria are met when the clinical health record includes non-binarynumeric data (e.g., data sufficient to provide a multi-point graph). Insome embodiments, in accordance with the first set of graphic criterianot being met, the first representation does not include the graphicalindication of the first clinical health record (e.g., a graph of thehealth data in the clinical health record). In some embodiments, thefirst set of graphic criteria are met when the clinical health recordincludes non-binary numeric data (e.g., data sufficient to provide amulti-point graph).

In some embodiments, the first representation includes a first detail(e.g., first information, first piece of data, within the record) of thefirst clinical health record. In some embodiments, the secondrepresentation includes the first detail and a second detail, differentfrom the first detail, of the first clinical health record. In someembodiments, the fourth representation includes the first detail, thesecond detail, and a third detail, different from the first and seconddetails, of the first clinical health record. In some embodiments, therepresentation of the first clinical health record becomes progressivemore detailed, as the hierarchy of the user interface is traversed.

In some embodiments, the second user interface includes a graphicalrepresentation (e.g., a graph) of a first portion (e.g., a portioncorresponding to a first time period) of the first clinical healthrecord data. In some embodiments, the graphical representation includesan indication of a relationship (e.g., a comparison) between a firstsub-portion of the first clinical health record data and a secondsub-portion of the first clinical health record data.

In some embodiments, the second user interface includes a firstaffordance. In some embodiments, the electronic device receives an inputcorresponding to selection of the first affordance. In some embodiments,in response to receiving the input corresponding to selection of thefirst affordance, the electronic device visually distinguishes (e.g.,emphasizing, highlighting, deemphasizing) a portion of the graphicalrepresentation that corresponds to a first sub-portion of the firstportion of the first clinical health record data that matches a firstfilter condition (e.g., a filter that identifies data that falls outsideof a clinical range (e.g., a healthy range) for the first clinicalhealth record data).

Visually distinguishing a portion of the graphical representation thatcorresponds to an aspect that matches a first filter condition providesthe user with feedback that the first filter condition has been matched.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first clinical health record of the first typeof clinical health record was received from (e.g., was sourced from, wasgenerated by) a first data source (e.g., data supplier; a clinicalhealth data source (e.g., a clinician)). In some embodiments, the secondclinical health record of the first type of clinical health record wasreceived from a second data source that is different from the first datasource.

In some embodiments, the fourth representation includes an indication ofa data source (e.g., data provider) of the first clinical health record.In some embodiments, the fourth representation includes an indication ofa primary identifier (e.g., a primary name, such as Hemoglobin A1c) ofthe first type of clinical health record and a secondary identifier(e.g., secondary or alternative name, such as Gylcated Hemoglobin,Glycosylated Hemoglobin, and HbAl c) of the first type of clinicalhealth record. In some embodiments, the fourth representation includesan indication of a first date corresponding to when the first clinicalhealth record was received by the electronic device and an indication ofa second date corresponding to when the first clinical health record wascreated (e.g., created by the electronic device or externally).

Note that details of the processes described above with respect tomethod 1000 (e.g., FIGS. 10A-10B) are also applicable in an analogousmanner to the methods described below/above. For example, methods 700,800, 900, 1100, and 1400 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1000. For brevity, these details are not repeated below.

FIGS. 11A-11C is a flow diagram illustrating a method for display ofhealth-related information using an electronic device in accordance withsome embodiments. Method 1100 is performed at a device (e.g., 100, 300,500, 600) with a display device. Some operations in method 1100 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 1100 provides an intuitive way for display ofhealth-related information. The method reduces the cognitive burden on auser for viewing health-related information, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to view health-related information faster andmore efficiently conserves power and increases the time between batterycharges.

The electronic device receives (1102) request (e.g., request to viewsearch user interface 684) to display a first user interface (e.g.,search user interface 684) (e.g., a request to view a search tab of ahealth application, such as a user tapping on an icon for the healthapplication or a user tapping on an affordance for the search tab).

In response to receiving the first request, the electronic devicedisplays (1104), via the display device, the first user interface (e.g.,search user interface 684) (e.g., the search tab of the healthapplication). The first user interface includes a first portion (e.g.,684 c) (1106) (e.g., a health category section), including a firstcategory affordance (e.g., 684 ca) (e.g., activity affordance) (e.g., acategory of health data; a category of biometric sensor data; anactivity category). The first user interface includes a second portion(e.g., 684 b) (1108) (e.g., a shared health data section) including afirst shared affordance (e.g., 684 ba) (e.g., Little Appleseedaffordance) corresponding to a second user account (e.g., LittleAppleseed account). In some embodiments, the second portion is includedin the first user interface in accordance with a determination that thefirst user account is associated with a second user account (e.g., achild account) different from the first user account.

While (1110) displaying the first user interface, the electronic devicereceives (1112) first user input corresponding to selection of the firstcategory affordance. While (1110) displaying the first user interface,the electronic device receives (1114) second user input corresponding toselection of the first shared affordance.

In response to receiving the first user input, the electronic devicedisplays (1116), via the display device, a second user interface (e.g.,686) (e.g., a user interface with health data for the selected healthcategory, such as activity, for a user's account associated with theelectronic device), including a representation (e.g., 686 a) of firsthealth data (e.g., a first discrete health record) associated with thefirst user account for the first category (e.g., activity).

In response to receiving the second user input, the electronic devicedisplays (1118), via the display device, a third user interface (e.g.,690) (e.g., a user interface with health categories for LittleAppleseed). The third user interface includes a first portion (e.g., 692b). The first portion includes a second category affordance (e.g., anactivity affordance) corresponding to health data associated with thesecond user account for the first category (e.g., activity).

While displaying the third user interface, the electronic devicereceives (1120) third user input corresponding to selection of thesecond category affordance. In response to receiving the third userinput, the electronic device displays (1122), via the display device, afourth user interface (e.g., 694) (e.g., a user interface with healthdata for the selected health category, such as activity, for LittleAppleseed), including a representation (e.g., 694 c) of health dataassociated with the second user account for the first category.

In some embodiments, the first health data associated with the firstuser account for the first category is also associated with the firstuser account for a second category (e.g., the first health data isrepresented in multiple categories accessible from the first userinterface). In some embodiments, the first user interface includes asecond category affordance corresponding to health data associated withthe first user account for a second category different from the firstcategory and, in response to a user input corresponding to the secondcategory affordance, an additional (e.g., a fourth) user interface isdisplayed that includes the first health data (e.g., 688).

In some embodiments, the fourth user interface does not include anoption (e.g., an editing affordance; any options) for modifying therepresentation of health data associated with the second user accountfor the first category (or, in some embodiments, for modifying thehealth data associated with the second user account for the firstcategory).

In some embodiments, while displaying the first user interface, theelectronic device receives a first set of inputs corresponding to arequest to search health data accessible to the electronic device (e.g.,health data stored on the electronic device, health data stored on aremote device (e.g., a server) that is accessible to the electronicdevice), including one or more inputs corresponding to entry of a searchstring (e.g., a text string of one or more characters). In someembodiments, the first user interface includes a search field and theone or more inputs correspond to entry of the search string are providedin the search field (e.g., FIG. 6U).

In some embodiments, in response to receiving the set of inputs, theelectronic device displays a plurality of search results including: afirst set of one or more search results including a representation ofsecond health data associated with the first user account, wherein thesecond health data associated with the first user account is associatedwith a first source (e.g., one or more sensors of the electronic device,one or more sensors of an external device that is associated with thefirst user account, an external device that is not associated with thefirst user account (e.g., a clinical source)); and a second set of oneor more search results including a representation of third health dataassociated with the first user account, wherein the third health dataassociated with the first user account is associated with a secondsource different from the first source (e.g., FIG. 6U).

Displaying search results including representations of health data fromdifferent sources provides the user with feedback about health data fromvarying sources on a single user interface. Providing improved visualfeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, as a part of displaying the plurality of searchresults, the electronic device ceases to display the first portion andthe second portion of the first user interface (e.g., FIG. 6U).

Ceasing to display the first portion and the second portion of the firstuser interface enables the device to display other content at those samelocations. Increasing the availability of display space for contentenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the first user interface includes a third portion(e.g., 684 d) including a first health record affordance that, whenselected, displays a representation of health data associated with thefirst user account that was received from a first external source (e.g.,clinical health records; health records provided by a medicalprofessional).

In some embodiments, the representation of health data associated withthe first user account for the first category corresponds to health datathat satisfied a set of formatting criteria (e.g., a set of criteriathat governs whether data is displayable in the second user interface).In some embodiments, health data (e.g., clinical health data) that isaccessible to the first electronic device is sorted based on whether thedata is in a format that can be parsed by one or more parsing processes.In some embodiments, the third portion includes a first affordance. Insome embodiments, the electronic device receives a fourth user inputcorresponding to selection of the first affordance. In some embodiments,in response to receiving the fourth user input, the electronic devicedisplays a set of health data that did not satisfy the set of formattingcriteria (e.g., 684 f).

Note that details of the processes described above with respect tomethod 1100 (e.g., FIGS. 11A-11C) are also applicable in an analogousmanner to the methods described below/above. For example, methods 700,800, 900, 1000, and 1400 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1100. For brevity, these details are not repeated below.

FIGS. 12AA-12AB depict an all health data user interface. In someexamples, the all health data user interface is displayed in response toselection of all health data affordance 628 depicted in FIG. 6DA. FIGS.12BA-12BB depict an XYZ Medical Center user interface. In some examples,the XYZ Medical Center user interface is displayed in response toselection of third notification affordance 620 depicted in FIG. 6DA,first health records affordance 636 depicts in FIG. 6DC, or title 670 adepicted in FIG. 6PA. FIG. 12C depicts an albuterol user interface. Insome examples, the albuterol user interface is displayed in response toselection of albuterol affordance in FIG. 12BA. FIG. 12D depicts ahematocrit user interface. In some examples, the hematocrit userinterface is displayed in response to selection of hematocrit affordancein FIG. 6PB, hematocrit affordance in FIG. 6Q, or hematocrit affordancein FIG. 12BB. FIGS. 12E-12F depicts a medications user interface. Insome examples, the medications user interface is displayed in responseto selection of affordance 666F in FIG. 60B, medications affordance inFIG. 12AA, or medications affordance in FIG. 12BA. FIGS. 12G-12I depictsuser interfaces related to a profile. In some examples, the userinterface are navigated to by selecting a picture on a user interfacematching the picture at the top of FIG. 12G.

FIGS. 13A-13G illustrate exemplary user interfaces related to sharinghealth data, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 14A-14B.

FIG. 13A depicts first electronic device 600 displaying health userinterface 1304 via touch-sensitive display device 602 at a first time.In some examples, first electronic device 600 includes one or morefeatures of devices 100, 300, 500, 606.

Health user interface 1304 relates to health data for a user associatedwith first electronic device 600 (e.g., the user logged into a firstaccount via first electronic device 600). Health user interface 1304includes a number of affordances, including child's health dataaffordance 1304 a. In some examples, selection of child's health dataaffordance 1304 a causes a user interface (e.g., share user interface1306 as depicted in FIG. 13B) to be displayed, as further discussedbelow.

FIG. 13A depicts first electronic device 600 receiving user input 1305corresponding to child's health data affordance 1304 a. In someexamples, user input 1305 is received via touch-sensitive display device602 and corresponds to a selection gesture (e.g., tap) on child's healthdata affordance 1304 a. In other examples, other forms of selection canbe used, such as a click using a mouse. In some examples, user input1305 causes a different user interface to be displayed viatouch-sensitive display device 602, such as display of share userinterface 1306 as depicted in FIG. 13B. In other examples, user input1305 causes a request to be sent to a second electronic devicerequesting for the second electronic device to share health data withfirst electronic device 600. In such examples, the second electronicdevice is associated with a second account different from but linked tothe first account (e.g., the second account corresponds to a childaccount of the first account).

FIG. 13B depicts first electronic device 600 displaying share userinterface 1306 via touch-sensitive display device 602 at a second timeafter the first time. In some examples, share user interface 1306 isdisplayed in response to (e.g., without any additional user input)selection of child's health data affordance 1304 a on health userinterface 1304, as depicted in 13A.

Share user interface 1306 includes request affordance 1304 a. Selectionof request affordance 1304 a causes a request to be sent to a secondelectronic device (e.g., second electronic device 1308) for the secondelectronic device to share health data with first electronic device 600.In some examples, before displaying share user interface 1306, a userinterface to identify an account for which to request to share isdisplayed (e.g., to identify Emma's account) (not illustrated).

FIG. 13C depicts second electronic device 1308 displaying notification1312 via touch-sensitive display device 1310 at a third time after thesecond time. In some examples, notification 1312 is a notification thatwas issued (e.g., caused to be displayed by second electronic device1308) from a process executing on second electronic device 1308. Forexample, the process can be a health process associated with a healthapplication. In some examples, notification 1312 is issued in responseto a determination that a user associated with first electronic device600 has requested for second electronic device 1308 to share health datawith first electronic device 600, as depicted in FIG. 13B.

As depicted in FIG. 13C, notification 1312 includes allow affordance1323 a and don't allow affordance 1323 b. Selection of allow affordance1323 a causes second electronic device 1308 to initiate a process forsending health data to first electronic device 600. For example, secondelectronic device 1308 transitions into a mode where new health datathat is associated with second electronic device 1308 is sent to firstelectronic device 600 for display via first electronic device 600. Insome examples, selection of allow affordance 1323 a also causes secondelectronic device 1308 to initiate a process for sending old health datato first electronic device 600 (e.g., health data associated with secondelectronic device 1308 that was obtained before selection of allowaffordance 1323 a).

In some examples, selection of don't allow affordance 1323 b causessecond electronic device 1308 to not share health data with firstelectronic device 600. In some examples, selection of don't allowaffordance 1323 b also causes health data from second electronic device1308 to not be backed up to another device (e.g., a backup server) dueto the selection causing there to not be memory allocated for secondelectronic device 1308 on a backup server (e.g., health cloud space isnot created for the second account when second electronic device 1308selects don't allow affordance 1323 b). In other examples, selection ofdon't allow affordance 1323 b causes health data from second electronicdevice 1308 to still be backed up to another device (e.g., a backupserver) (e.g., health cloud space is created for the second account whensecond electronic device 1308 selects don't allow affordance 1323 b). Insome examples, backup data associated with second electronic device 1308is separate from backup data associated with first electronic device 600(e.g., first electronic device 600 stores its health data in a separatelocation from second electronic device 1308).

FIG. 13D depicts first electronic device 600 displaying health userinterface 1304 via touch-sensitive display device 602 at a fourth timeafter the third time. Health user interface 1304 depicted in FIG. 13D isthe same user interface depicted in FIG. 13A. The difference with healthuser interface 1304 as depicted in FIG. 13D is that it includes healthdata section 1314 with multiple affordances associated with secondelectronic device 1308. In some examples, health data section 1314 isincluded in health user interface 1304 in response to selection of allowaffordance 1323 a on second electronic device 1308 (as depicted in FIG.13C).

Health data section 1314 includes health data affordance 1314 a and stopaffordance 1314 b. In some examples, health data affordance 1314 a, whenselected, causes first electronic device 600 to display a user interface(e.g., a user interface corresponding to the health application) withhealth data corresponding to Emma (e.g., the user associated with secondelectronic device 1308). An example of such a user interface is depictedin FIGS. 6XA-6XB.

In some examples, stop affordance 1314 b, when selected, causes firstelectronic device 600 to (1) stop receiving health data corresponding tosecond electronic device 1308 and (2) delete any health datacorresponding to second electronic device 1308 that is stored in memoryassociated with first electronic device 600 (e.g., health datacorresponding to second electronic device 1308 is not deleted fromsecond electronic device 1308 or another device used to backup healthdata corresponding to second electronic device 1308 (e.g., a backupserver)).

FIG. 13E depicts second electronic device 1308 displaying notification1316 via touch-sensitive display device 1310 at a fifth time after thefourth time. In some examples, notification 1316 is a notification thatwas issued (e.g., caused to be displayed by second electronic device1308) from a process executing on second electronic device 1308. Forexample, the process can be a health process associated with a healthapplication. In some examples, notification 1316 is issued in responseto a determination that second electronic device 1308 is sharing healthdata with first electronic device 600 and a predefined, non-zero amountof time (e.g., a few days, a few weeks, a few months, or the like) haspassed since second electronic device 1308 has begun sharing health datawith first electronic device 600. In some examples, multiple suchnotifications are issued at different times.

As depicted in FIG. 13E, notification 1318 includes view affordance 1316a and dismiss affordance 1316 b. Selection of view affordance 1316 acauses second electronic device 1308 to display a different userinterface via touch-sensitive display device 602, such as sharingoptions user interface 1318 as depicted in FIG. 13F. In other examples,selection of view affordance 1316 a causes first electronic device 600to (1) stop receiving health data corresponding to second electronicdevice 1308 and (2) delete any health data corresponding to secondelectronic device 1308 that is stored in memory associated with firstelectronic device 600 (e.g., health data corresponding to secondelectronic device 1308 is not deleted from second electronic device 1308or another device used to backup health data corresponding to secondelectronic device 1308 (e.g., a backup server)). Selection of dismissaffordance 1316 b causes second electronic device 1308 to forgo displayof notification 1316.

FIG. 13E depicts second electronic device 1308 receiving user input 1317corresponding to view affordance 1316 a. In some examples, user input1317 is received via touch-sensitive display device 1310 and correspondsto a selection gesture (e.g., tap) on view affordance 1316 a. In otherexamples, other forms of selection can be used, such as a click using amouse. As discussed above, in some examples, user input 1317 causes adifferent user interface to be displayed (e.g., sharing options userinterface 1318, as depicted in FIG. 13F).

FIG. 13F depicts second electronic device 1308 displaying sharingoptions user interface 1318 via touch-sensitive display device 1310 at asixth time after the fifth time. In some examples, sharing options userinterface 1318 is displayed in response to (e.g., without any additionaluser input) selection of view affordance 1316 a on notification 1316, asdepicted in 13E.

Sharing options user interface 1318 includes stop affordance 1318 a,backup affordance 1318 b, and off affordance 1318 c. Selection of stopaffordance 1318 a causes second electronic device 1308 to initiate aprocess to stop sharing health data with first electronic device 600.The process causes first electronic device 600 to (1) stop receivinghealth data corresponding to second electronic device 1308 and (2)delete any health data corresponding to second electronic device 1308that is stored in memory associated with first electronic device 600(e.g., health data corresponding to second electronic device 1308 is notdeleted from second electronic device 1308 or another device used tobackup health data corresponding to second electronic device 1308 (e.g.,a backup server)). In some examples, selection of stop affordance 1318 acauses multiple devices (in addition to first electronic device 600)(e.g., all devices for which second electronic device 1308 is sharinghealth data with) to (1) stop receiving health data corresponding tosecond electronic device 1308 and (2) delete any health datacorresponding to second electronic device 1308 that is stored in memoryassociated with the respective device 600 (e.g., health datacorresponding to second electronic device 1308 is not deleted fromsecond electronic device 1308 or another device used to backup healthdata corresponding to second electronic device 1308 (e.g., a backupserver)).

In some examples, selection of stop affordance 1318 a does not stopsecond electronic device 1308 from sharing health data with anotherdevice used to backup health data corresponding to second electronicdevice 1308 (e.g., a backup server) (e.g., second electronic device 1308continues to backup health data to the backup server). In some examples,selection of stop affordance 1318 a also causes health data section 1314to be removed from health user interface 1304 on first electronic device600. In some examples, when first electronic device 600 is receivinghealth data from at least one other device according to techniquesdescribed herein, selection of stop affordance 1318 a causes userinterface elements related to second electronic device 1308 to beremoved from health data section 1314 but health data section 1314 willstill be included in health user interface 1304 on first electronicdevice 600 for the other device.

Selection of backup affordance 1318 b causes second electronic device1308 to stop sending health data to another device used to backup healthdata corresponding to second electronic device 1308 (e.g., a backupserver). In some examples, selection of backup affordance 1318 b alsocauses the other device to delete health data corresponding to secondelectronic device 1308 such that the health data corresponding to secondelectronic device 130 is only stored on second electronic device 1308.

Selection of off affordance 1318 c causes second electronic device 1308to (1) turn off (e.g., stop) collection of health data corresponding tosecond electronic device 1308, (2) stop sending health data to anotherdevice used to backup health data corresponding to second electronicdevice 1308 (e.g., a backup server), (3) cause other devices to deletehealth data corresponding to second electronic device 1308 such that thehealth data corresponding to second electronic device 1308 is not storedon other devices, or (4) any combination thereof.

FIG. 13F depicts second electronic device 1308 receiving user input 1319corresponding to stop affordance 1318 a. In some examples, user input1319 is received via touch-sensitive display device 1310 and correspondsto a selection gesture (e.g., tap) on stop affordance 1318 a. In otherexamples, other forms of selection can be used, such as a click using amouse. As discussed above, in some examples, user input 1318 a causessecond electronic device 1308 to initiate a process to stop sharinghealth data with first electronic device 600. The process causes firstelectronic device 600 to (1) stop receiving health data corresponding tosecond electronic device 1308, (2) delete any health data correspondingto second electronic device 1308 that is stored in memory associatedwith first electronic device 600 (e.g., health data corresponding tosecond electronic device 1308 is not deleted from second electronicdevice 1308 or another device used to backup health data correspondingto second electronic device 1308 (e.g., a backup server)), and (3)health data section 1314 to be removed from health user interface 1304on first electronic device 600, as depicted in 13G.

FIG. 13G depicts first electronic device 600 displaying health userinterface 1304 via touch-sensitive display device 602 at a seventh timeafter the sixth time. As depicted in FIG. 13G, health user interface1304 no longer includes health data section 1314 (as depicted in FIG.13D).

FIGS. 14A-14B is a flow diagram illustrating a method for managingshared health data using an electronic device in accordance with someembodiments. Method 1400 is performed at a device (e.g., 100, 300, 500,600, 606, 1308) with a display device. Some operations in method 1400are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 1400 provides an intuitive way for related tosharing health data. The method reduces the cognitive burden on a userfor managing shared health data, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to manage shared health data faster and more efficientlyconserves power and increases the time between battery charges.

The first electronic device receives (1402) a request (e.g., 1307) toshare health data associated with (e.g., detected by) the firstelectronic device. In some embodiments, the request to share is sent tothe first electronic device in response to a second electronic devicerequesting that the first electronic device share health data.

In response to receiving the request, the first electronic devicedisplays (1404), via the display device at a first time, a firstnotification (e.g., 1312) (e.g., a notification indicating that thesecond electronic device is requesting that the first electronic deviceshare health data with the first electronic device), including a firstaffordance (e.g., 1323 a) (e.g., an allow affordance) that, whenselected, initiates a process for sharing of health data, associatedwith the first electronic device, with a second electronic device.

While displaying the notification, the first electronic device receives(1406) a first user input corresponding to selection of the firstaffordance.

In response to receiving the first user input, the first electronicdevice initiates (1408) a process for sharing of health data, associatedwith the first electronic device, with the second electronic device.

After (1410) receiving the first user input, the first electronic deviceshares (1412) health data associated with the first electronic devicewith the second electronic device. In some embodiments, the sending isperformed in response to receiving the first user input. After (1410)receiving the first user input, the first electronic device displays(1414), via the display device at a second time, a second notification(e.g., 1316) (e.g., a notification to confirm that a user associatedwith the first electronic device wishes to share health data with thesecond electronic device) corresponding to the sharing of health data,the second notification including a second affordance (e.g., 1316 a)that, when selected, initiates a process to end sharing of health data,associated with the first electronic device, with the second electronicdevice. In some embodiments, the second notification is displayed at adifferent time than the sending, such as a few days after receiving thefirst user input. In some embodiments, the second notification isdisplayed after the sending. In some embodiments, while displaying thesecond notification, receiving a set of one or more inputs that includesan input corresponding to selection of a third affordance (e.g., 1318a); and in response to receiving the set of one or more inputs (e.g.,1319), ceasing to share health data, associated with the firstelectronic device, with the second electronic device.

Displaying a notification that enables a user to end sharing of healthdata provides the user with feedback that the health data is beingshared and enables the user to more efficiently access the interface forending the sharing of the health data. Providing improved visualfeedback to the user and reducing the number of inputs needed to performan operation enhance the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while displaying the second notification, the firstelectronic device receives a set of one or more inputs that includes aninput corresponding to selection of the second affordance (e.g., 1317).In some embodiments, in response to receiving the set of one or moreinputs, the first electronic device ceases to share health data,associated with the first electronic device, with the second electronicdevice.

In some embodiments, after receiving the first user input, the firstelectronic device shares health data associated with the firstelectronic device with a third electronic device (e.g., a server storinghealth related data associated with the first electronic device). Insome embodiments, after receiving the set of one or more inputs, thefirst electronic device continues to share health data associated withthe first electronic device with the third electronic device (e.g.,selection of the second affordance does not cause the device to stopsharing health data with the third electronic device).

In some embodiments, the first notification includes a third affordance(e.g., 1323 b) (e.g., a “do not allow sharing” affordance) that, whenselected: causes the first electronic device to forgo initiating aprocess for sharing of health data, associated with the first electronicdevice, with the second electronic device (and, in some embodiments,transmitting information to the second electronic device indicating thatthe request to share health data was not granted); and causes the firstelectronic device to transmit a request to a fourth electronic device(e.g., a server storing health related data associated with the firstelectronic device) to accept health data (e.g., to allocate storageresources to accept health data) associated with the first electronicdevice.

In some embodiments, the first notification includes a fourth affordance(e.g., 1323 b) (e.g., a “do not allow sharing” affordance) that, whenselected: causes the first electronic device to forgo initiating aprocess for sharing of health data, associated with the first electronicdevice, with the second electronic device (and, in some embodiments,transmitting information to the second electronic device indicating thatthe request to share health data was not granted); and causes the firstelectronic device to transmit a request to a fifth electronic device(e.g., a server storing health related data associated with the firstelectronic device) to accept health data (e.g., to allocate storageresources to accept health data) associated with the first electronicdevice.

In some embodiments, the first electronic device is associated with afirst user account (e.g., a primary user account; a health-related useraccount) and second electronic device is associated with a second useraccount that is different from the first user account.

Note that details of the processes described above with respect tomethod 1400 (e.g., FIGS. 14A-14B) are also applicable in an analogousmanner to the methods described below/above. For example, methods 700,800, 900, 1000, and 1100 optionally include one or more of thecharacteristics of the various methods described above with reference tomethod 1400. For brevity, these details are not repeated below.

FIGS. 15A-5F depict a flow through a heath user interface within asettings user interface on second electronic device 1308.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve themanagement and delivery of health information to users. The presentdisclosure contemplates that in some instances, this gathered data caninclude personal information data that uniquely identifies or can beused to contact or locate a specific person. Such personal informationdata can include demographic data, location-based data, telephonenumbers, email addresses, twitter IDs, home addresses, data or recordsrelating to a user's health or level of fitness (e.g., vital signsmeasurements, medication information, exercise information), date ofbirth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver appropriate notifications and health summaries to the user.Accordingly, use of such personal information data enables users tomanage their health information more efficiently. Further, other usesfor personal information data that benefit the user are alsocontemplated by the present disclosure. For instance, health and fitnessdata can be used to provide insights into a user's general wellness, orcan be used as positive feedback to individuals using technology topursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof accessing or storing health information, the present technology canbe configured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In another example,users can select not to provide certain types of health-relatedinformation. In yet another example, users can select to limit thelength of time health-related information is maintained or entirelyprohibit the storage of health-related information. In addition toproviding “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data.

What is claimed is:
 1. An electronic device associated with a first useraccount, comprising: a display device; one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:receiving a first request to display a first user interface; in responseto receiving the first request, displaying, via the display device, thefirst user interface, including: a first portion, including a firstcategory affordance; and a second portion including a first sharedaffordance corresponding to a second user account; while displaying thefirst user interface: receiving first user input corresponding toselection of the first category affordance; and receiving second userinput corresponding to selection of the first shared affordance; inresponse to receiving the first user input, displaying, via the displaydevice, a second user interface, including a representation of firsthealth data associated with the first user account for a first category;in response to receiving the second user input, displaying, via thedisplay device, a third user interface, including: a first portion,including: a second category affordance corresponding to health dataassociated with the second user account for the first category; whiledisplaying the third user interface, receiving third user inputcorresponding to selection of the second category affordance; and inresponse to receiving the third user input, displaying, via the displaydevice, a fourth user interface, including a representation of healthdata associated with the second user account for the first category. 2.The electronic device of claim 1, wherein the first health dataassociated with the first user account for the first category is alsoassociated with the first user account for a second category.
 3. Theelectronic device of claim 1, wherein the fourth user interface does notinclude an option for modifying the representation of health dataassociated with the second user account for the first category.
 4. Theelectronic device of claim 1, the one or more programs further includinginstructions for: while displaying the first user interface, receiving afirst set of inputs corresponding to a request to search health dataaccessible to the electronic device, including one or more inputscorresponding to entry of a search string; and in response to receivingthe first set of inputs, displaying a plurality of search resultsincluding: a first set of one or more search results including arepresentation of second health data associated with the first useraccount, wherein the second health data associated with the first useraccount is associated with a first source; and a second set of one ormore search results including a representation of third health dataassociated with the first user account, wherein the third health dataassociated with the first user account is associated with a secondsource different from the first source.
 5. The electronic device ofclaim 4, wherein: displaying the plurality of search results includesceasing to display the first portion and the second portion of the firstuser interface.
 6. The electronic device of claim 1, wherein the firstuser interface includes a third portion including a first health recordaffordance that, when selected, displays a representation of health dataassociated with the first user account that was received from a firstexternal source.
 7. The electronic device of claim 6, wherein: therepresentation of health data associated with the first user account forthe first category corresponds to health data that satisfied a set offormatting criteria; and the third portion includes a first affordance,the one or more programs further including instructions for: receiving afourth user input corresponding to selection of the first affordance;and in response to receiving the fourth user input, displaying a set ofhealth data that did not satisfy the set of formatting criteria.
 8. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device, associated with a first user account, with a displaydevice, the one or more programs including instructions for: receiving afirst request to display a first user interface; in response toreceiving the first request, displaying, via the display device, thefirst user interface, including: a first portion, including a firstcategory affordance; and a second portion including a first sharedaffordance corresponding to a second user account; while displaying thefirst user interface: receiving first user input corresponding toselection of the first category affordance; and receiving second userinput corresponding to selection of the first shared affordance; inresponse to receiving the first user input, displaying, via the displaydevice, a second user interface, including a representation of firsthealth data associated with the first user account for a first category;in response to receiving the second user input, displaying, via thedisplay device, a third user interface, including: a first portion,including: a second category affordance corresponding to health dataassociated with the second user account for the first category; whiledisplaying the third user interface, receiving third user inputcorresponding to selection of the second category affordance; and inresponse to receiving the third user input, displaying, via the displaydevice, a fourth user interface, including a representation of healthdata associated with the second user account for the first category. 9.A method, comprising: at an electronic device with a display device,wherein the electronic device is associated with a first user account:receiving a first request to display a first user interface; in responseto receiving the first request, displaying, via the display device, thefirst user interface, including: a first portion, including a firstcategory affordance; and a second portion including a first sharedaffordance corresponding to a second user account; while displaying thefirst user interface: receiving first user input corresponding toselection of the first category affordance; and receiving second userinput corresponding to selection of the first shared affordance; inresponse to receiving the first user input, displaying, via the displaydevice, a second user interface, including a representation of firsthealth data associated with the first user account for a first category;in response to receiving the second user input, displaying, via thedisplay device, a third user interface, including: a first portion,including: a second category affordance corresponding to health dataassociated with the second user account for the first category; whiledisplaying the third user interface, receiving third user inputcorresponding to selection of the second category affordance; and inresponse to receiving the third user input, displaying, via the displaydevice, a fourth user interface, including a representation of healthdata associated with the second user account for the first category.